A procedure for turning a bug report, error log, or monitoring alert into a structured GitHub issue.

Use it to verify reproduction, classify severity from critical to low, identify the affected area, and write the issue with expected and actual behavior.

It makes the problem easier to reproduce, prioritize, route to the right area, and assign to someone for fixing.

bug-triage — Skill for Claude Code and Codex by zakelfassi: A procedure for turning a bug report, error log…

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.

agentmods

npx agentmods add skills/zakelfassi/skills-driven-development/bug-triage

Any agent

npx skills add zakelfassi/skills-driven-development --skill bug-triage

Clone the repo

git clone --depth 1 https://github.com/zakelfassi/skills-driven-development

Made for: Claude Code, Codex.

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/zakelfassi/skills-driven-development/bug-triage.svg)](https://agentmods.dev/skills/zakelfassi/skills-driven-development/bug-triage)

Your own site

<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/bug-triage"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/bug-triage.svg" alt="Measured on agentmods" height="20"></a>

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

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

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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	$0.00049	$0.00724
Opus 5	$0.00024	$0.00362
Sonnet 5	$0.00010	$0.00145
Haiku 4.5	$0.00005	$0.00072

Measured 4d ago against content hash 6031519aa84d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 4d 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.

examples/webapp-starter/skills/bug-triage/SKILL.md · 86 lines

How it starts

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

Bug Triage

Convert a bug report (user message, error log, Sentry alert) into a well-structured GitHub issue.

Inputs

Bug report (raw text, screenshot, error log, or Sentry URL)
Reporter (who reported it, if known)
Environment (production, staging, local)

Steps

Reproduce or verify
- Can you reproduce the bug from the report?
- If yes: document exact reproduction steps
- If no: flag as "needs-repro" and note what you tried

Classify severity

Severity	Criteria	Label
P0	Data loss, security, or full outage	`severity:critical`
P1	Major feature broken, no workaround	`severity:high`
P2	Feature broken, workaround exists	`severity:medium`
P3	Minor annoyance, cosmetic	`severity:low`

Identify the component
- Frontend / Backend / Infrastructure / Extension
- Add the corresponding label: area:frontend, area:backend, etc.

Write the GitHub issue

## Bug: [one-line description]

**Severity:** P[0-3]
**Environment:** [production/staging/local]
**Reporter:** [name or "internal"]

### What happened
[Clear description of the bug]

### Expected behavior
[What should have happened]

### Reproduction steps
1. ...
2. ...
3. ...

### Evidence
[Error logs, screenshots, Sentry link]

### Suspected cause
[If you have a hypothesis, state it]

File the issue

gh issue create --title "Bug: [description]" --body "[body]" --label "bug,severity:[level],area:[component]"

Assign if obvious
- If the suspected cause points to a clear owner, assign them
- If not, leave unassigned (triage meeting will handle it)

Conventions

Bug titles always start with Bug:
Every bug issue has both a severity: and area: label
P0 bugs get a Slack notification (via scripts/notify-critical.sh)
Duplicate bugs are closed with a reference to the original

Read the full file on GitHub · 86 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.

4d ago First seen · 86 lines · 49 tokens per session scan A 6031519aa84d

Subscribe to this mod's changes

bug-triage is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 724 once invoked, about $0.0002 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-08-30.

Debugging agent-skills agentic-development ai ai-agents developer-tools skills

claude-md-improver

Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…

anthropics/claude-plugins-official · 82 tokens

agent-platform-rag-engine-management

Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…

google/skills · 85 tokens

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

google/skills · 60 tokens

twitter-reader

Read Twitter/X for financial research using opencli (read-only). Use this skill whenever the user wants to read their Twitter feed, search for financial tweets, view bookmarks, look up user profiles, or gather market sentiment from Twitter/X. Triggers include: "check my feed", "search Twitter for", "show my…

himself65/finance-skills · 161 tokens

chenhao-limit-up

Use when evaluating A-share limit-up (涨停板) setups through Chen Hao's sentiment and momentum lens: market emotion cycles, board strength, follow-through, and short-term aggressive momentum trading.

questflowai/investorskills · 44 tokens

comet-github

将 Comet GitHub 维护请求路由到基于证据的 PR 审阅、Issue 分诊、本地想法收集、CI 诊断或 Issue 实施流程。用户提到 Comet GitHub Issue/PR 但未指定流程，或询问下一步如何处理时使用。.

rpamis/comet · 72 tokens