Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/cenconq25/claude-code-app-studio/bug-reportnpx skills add cenconq25/claude-code-app-studio --skill bug-reportgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/bug-report)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/bug-report"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/bug-report.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00053 | $0.01673 |
| Opus 5 | $0.00026 | $0.00837 |
| Sonnet 5 | $0.00011 | $0.00335 |
| Haiku 4.5 | $0.00005 | $0.00167 |
Grade A, and why
bug-report scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Report
Turn a vague observation into a fileable, actionable defect record. Three input modes — user description, target code/files, or a crash log.
Phase 1: Pick the Mode
If --from-description (or no flag): collect details from the user via
AskUserQuestion.
If --from-code=<path>: read the specified file(s) and look for likely
bugs (unsafe optionals, race conditions, leaked subscriptions, etc.).
If --from-crashlog=<path>: read the crash log, identify the failing
stack frame, and reverse-engineer steps.
Phase 2A: From User Description
Walk through these prompts via AskUserQuestion in order:
- Title — one line, action + outcome ("Sign-in fails after biometric prompt cancel").
- Severity — S1 (crash, data loss, blocks release), S2 (major feature broken, no workaround), S3 (minor feature broken, workaround exists), S4 (cosmetic).
- Affected platforms — iOS / Android / both.
- Device(s) reproduced on — model + OS version. List all confirmed.
- Build version + commit SHA — the build under which the bug was seen.
- Reproduction steps — numbered, unambiguous. Each step should be verifiable on a fresh install.
- Expected result.
- Actual result.
- Frequency — every time / often (>50%) / sometimes / once.
- Attachments — screenshots, screen recordings, crash logs, charles captures, video file paths.
- Workaround — if any.
Keep collected answers in working memory and assemble them in Phase 4.
Phase 2B: From Code
Read the target file(s). Check for these patterns:
- Force-unwrapped optionals on user input.
- Unchecked array index access.
- Async work without cancellation that captures view state.
- Missing offline / error / loading branches.
- Non-idempotent network mutations (no idempotency key).
- Missing feature-flag fallbacks.
- Leaked subscriptions / observers (RN useEffect missing cleanup, Combine cancellables not stored, Flutter StreamSubscription not cancelled, Android Job not cancelled).
- Hardcoded keys, URLs, or environment names.
- Race conditions in
Promise.allordering. - Memory: closures capturing strong
selfin iOS, missing[weak self]. - Deep links accepting unsanitized parameters.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today First seen · 231 lines · 53 tokens per session scan A 3fbcb99da818
bug-report is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 1,673 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…