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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00053 | $0.01673 |
| Opus 5.5 | $0.00021 | $0.00669 |
| Sonnet 5.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 1mo ago.
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.
- 1mo ago 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 (42 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 1,673 once invoked, about $0.0002 per session on Opus 5.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
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue-reports
Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).