A workflow for reviewing open bug reports, rechecking their impact and urgency, assigning them to sprints, and finding recurring problem patterns.

Use it at sprint start, after new bugs are filed, or when the backlog needs reprioritisation. It can assign bugs, defer them, or produce a trend-only report.

It turns a growing bug backlog into a clear action list and helps prevent serious issues from being overlooked between sprints.

bug-triage — Skill for Claude Code by bullish0x

Install

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.

Any agent

npx skills add bullish0x/GameStudio --skill bug-triage

Clone the repo

git clone --depth 1 https://github.com/bullish0x/GameStudio

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bullish0x/gamestudio/bug-triage/github.svg)](https://agentmods.dev/skills/bullish0x/gamestudio/bug-triage)

Your own site

<a href="https://agentmods.dev/skills/bullish0x/gamestudio/bug-triage"><img src="https://agentmods.dev/badge/skills/bullish0x/gamestudio/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bullish0x/gamestudio/bug-triage"><img src="https://agentmods.dev/badge/skills/bullish0x/gamestudio/bug-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,010 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 97% copy Near-identical to another mod in the catalogue.

Token cost

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.00059	$0.02010
Opus 5	$0.00030	$0.01005
Sonnet 5	$0.00012	$0.00402
Haiku 4.5	$0.00006	$0.00201

Measured 5d ago against content hash f27637978fe0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 5d 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.

Origin

This is a copy

97% identical to bug-triage — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/bug-triage/SKILL.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bug Triage

This skill processes the open bug backlog into a prioritised, sprint-assigned action list. It distinguishes between severity (how bad is the impact?) and priority (how urgently must we fix it?), detects systemic trends, and ensures no critical bug is lost between sprints.

Output: production/qa/bug-triage-[date].md

When to run:

Sprint start — assign open bugs to the new sprint or backlog
After /team-qa completes and new bugs have been filed
When the bug count crosses 10+ open items

1. Parse Arguments

Modes:

/bug-triage sprint — triage against the current sprint; assign fixable bugs to the sprint backlog; defer the rest
/bug-triage full — full triage of all bugs regardless of sprint scope
/bug-triage trend — trend analysis only (no assignment); read-only report
No argument — run sprint mode if a current sprint exists, else full mode

2. Load Bug Backlog

Step 2a — Discover bug files

Glob for bug reports in priority order:

production/qa/bugs/*.md — individual bug report files (preferred format)
production/qa/bugs.md — single consolidated bug log (fallback)
Any production/qa/qa-plan-*.md "Bugs Found" table (last resort)

If no bug files found:

"No bug files found in production/qa/bugs/. If bugs are tracked in a different location, adjust the glob pattern. If no bugs exist yet, there is nothing to triage."

Stop and report. Do not proceed if no bugs exist.

Step 2b — Load sprint context

Read the most recently modified file in production/sprints/ to understand:

Current sprint number / name
Stories in scope (for assignment target)
Sprint capacity constraints (if noted)

If no sprint file exists: note "No sprint plan found — assigning to backlog only."

Step 2c — Load severity reference

Read .agents/docs/coding-standards.md for severity/priority definitions if they exist. If they do not exist, use the standard definitions in Step 3.

3. Classify Each Bug

Read the full file on GitHub · 244 lines

Changes

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.

5d ago First seen · 244 lines · 59 tokens per session scan A f27637978fe0

Subscribe to this mod's changes

bug-triage is a skill published in the GitHub repository bullish0x/GameStudio (11 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 2,010 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to bug-triage, differing in 3 lines, and is treated as a copy.

Claude Code Debugging Project management agents ai-agents ai-coding claude codex

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.

Gentleman-Programming/gentle-ai · 57 tokens

factory-triage

Triage a Factory work item's issue — trace history, understand architecture, diagnose root cause, then advance the stage.

mastra-ai/mastra · 27 tokens

customer-success

Support workflows, ticketing systems (Zendesk, Intercom), knowledge base design, chatbot design, and metrics (CSAT, NPS). Use when building support infrastructure, designing help centers, or optimizing customer experience.

travisjneuman/.claude · 47 tokens

event-planner

Event planning with timelines, budgets, vendor coordination, logistics checklists, and post-event evaluation. Use when organizing conferences, workshops, galas, or corporate events.

travisjneuman/.claude · 37 tokens

hr-talent

HR and talent management expertise for talent acquisition, performance management, compensation strategy, organizational design, culture building, succession planning, and D&I programs. Use when hiring, managing performance, designing organizations, or building culture.