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-triagegit 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-triage)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/bug-triage"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/bug-triage/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-triage"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/bug-triage.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.00044 | $0.01526 |
| Opus 5.5 | $0.00018 | $0.00610 |
| Sonnet 5.5 | $0.00009 | $0.00305 |
| Haiku 4.5 | $0.00004 | $0.00153 |
Grade A, and why
bug-triage 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Triage
Bring the bug backlog back under control. Read every open bug, refresh priorities against current reality, group by symptom, and assign each bug an owner and a sprint.
Phase 1: Inventory
Glob production/qa/bugs/BUG-*.md. Read each whose Status is Open,
In Progress, or Reopened. Skip Closed, WontFix, Duplicate.
Capture per bug:
- ID, title
- Current severity, priority, status
- Affected platforms
- Affected build (and whether that build is still relevant)
- Frequency
- File date
- Suspected area / module
- Last update date
Optional argument --since=<date> filters to bugs filed after a date.
Phase 2: Re-evaluate Each Bug
For every bug, ask whether the current severity/priority still fits. Drivers of re-evaluation:
- Build relevance — if the affected build is now several releases old, can the bug still be reproduced? Surface for user to confirm.
- Workaround stability — if a documented workaround has stopped working, severity goes up.
- Frequency drift — telemetry numbers (Crashlytics, Sentry) may show the bug occurring more or less often than at filing time.
- Business context — paywall bugs near a marketing push, auth bugs near an enterprise rollout, push bugs near a re-engagement campaign all elevate priority.
- Age — open longer than 30 days at S2 or above is a smell.
Read recent telemetry summary if present
(production/qa/telemetry-summary.md) and use it to inform the calls.
For each bug, propose new severity/priority. Use AskUserQuestion in batches:
question: "BUG-NNN: [title]\nCurrent: S[X]/P[Y] — proposed: S[A]/P[B]\nReason: [reason]"
options:
- "Accept proposal"
- "Keep current"
- "Override — let me set values"
- "Close — fixed / not reproducible / wontfix (specify)"
Phase 3: Detect Systemic Trends
Cluster the open bugs:
- By module (auth, paywall, sync, push, navigation).
- By symptom (crash, ANR, freeze, layout, copy, network, payment).
- By platform (iOS-only, Android-only, both).
- By cause hypothesis (race condition, leaked subscription, missing null check, deprecated API).
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 · 210 lines · 44 tokens per session scan A edea48425488
bug-triage is a skill published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 44 tokens to every session and 1,526 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).