A bug-reporting command that turns a plain description of a software problem into an investigation, documentation, and coordinated fix process.

Use it to report issues such as broken buttons, server errors, mobile failures, or slow pages and start the related investigation.

It provides a structured path from noticing a problem to reproducing it, finding its cause, and checking the fix.

bug — Command for Claude Code by olehsvyrydov/AI-development-team

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.

Clone the repo

git clone --depth 1 https://github.com/olehsvyrydov/AI-development-team

Made for: Claude Code.

Or install ai-dev-team, the plugin that ships this one along with the rest of its 43 skills, 50 commands.

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/commands/olehsvyrydov/ai-development-team/bug/github.svg)](https://agentmods.dev/commands/olehsvyrydov/ai-development-team/bug)

Your own site

<a href="https://agentmods.dev/commands/olehsvyrydov/ai-development-team/bug"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/bug/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/commands/olehsvyrydov/ai-development-team/bug"><img src="https://agentmods.dev/badge/commands/olehsvyrydov/ai-development-team/bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 894 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 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.1	$0.00019	$0.00894
Opus 5.5	$0.00008	$0.00358
Sonnet 5.5	$0.00004	$0.00179
Haiku 4.5	$0.00002	$0.00089

Measured 1mo ago against content hash 5ce1cff84a95, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

claude/commands/bug.md · 150 lines

How it starts

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

Bug Command

Report a bug with a simple description. Claude will handle investigation, structured documentation, and fix coordination.

Usage

/bug [description of the issue]

Examples

/bug I see internal server error in /approval page when I move from dashboard to users menu item

/bug Login button doesn't work on mobile Safari

/bug Performance is slow when loading the users list with more than 100 entries

What Happens

When you invoke /bug [description]:

Bug report created with temporary ID (BUG-XXX)
/sm (/luda) creates ticket:
- Sets priority (P0-P3) - consults /po, /arch, user, or suggests based on load
- Assigns investigator (/fe, /be, or /e2e based on bug type)
- Schedules in sprint
Investigation phase:
- Identify affected component (frontend/backend/mobile)
- Attempt to reproduce the issue
- Gather evidence (logs, screenshots, network requests)
- Identify root cause
- If cannot reproduce: /qa recommends close ticket OR request more info OR mark for monitoring
Reproduction test created by /qa (/rob):
- Write a failing test that proves the bug exists
- This test MUST fail now and pass after fix
Investigation report generated with:
- Root cause analysis
- Affected files/components
- Proposed fix approach
- Risk assessment
Fix phase (TDD):
- Read investigation report
- Verify reproduction test still fails
- Write unit tests (RED - tests fail)
- Implement fix (GREEN - tests pass)
- Refactor code
- All tests pass
Verified by /rev (code review) and /e2e (/adam) (automated tests), /sm closes ticket

Priority Levels

Priority	Criteria	Response
P0	System down, data loss, security	Immediate fix
P1	Major feature broken	Same day
P2	Feature impaired, workaround exists	Current sprint
P3	Minor, cosmetic	Backlog

Workflow

/bug [description]
     |
     v
+-------------------------+
| Bug report created      |
| (BUG-XXX)               |
+-----------+-------------+
            |
            v
+-------------------------+
| /sm creates ticket      |
| - Sets priority (P0-P3) |
| - Assigns investigator  |
| - Schedules in sprint   |
+-----------+-------------+
            |
            v
+-------------------------+
| INVESTIGATION PHASE     |
| - Identifies component  |
| - Reproduces issue      |
| - Finds root cause      |
| (if cannot reproduce:   |
|  close/more info/monitor|
+-----------+-------------+
            |
            v
+-------------------------+
| /qa writes failing      |
| reproduction test       |
+-----------+-------------+
            |
            v
+-------------------------+
| Investigation Report    |
| created and saved       |
+-----------+-------------+
            |
            v
+-------------------------+
| FIX PHASE (TDD)         |
| - Write unit tests (RED)|
| - Implement fix (GREEN) |
| - Refactor              |
| - All tests pass        |
+-----------+-------------+
            |
            v
+-------------------------+
| /rev reviews fix        |
| /e2e runs automated     |
| tests (verifies fix)    |
| /sm closes ticket       |
+-------------------------+

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

1mo ago First seen · 150 lines · 19 tokens per session scan A 5ce1cff84a95

Subscribe to this mod's changes

bug is a command published in the GitHub repository olehsvyrydov/AI-development-team (17 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 894 once invoked, about $0.0001 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-08-30.

Claude Code Code review Debugging agentic-workflow ai-agents ai-dev-tools anthropic

bug

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Bug Command

Usage

Examples

What Happens

Priority Levels

Workflow

What this file has done since we first saw it

Other commands, from other repositories

refactor-clean

deep-audit.skeleton

architecture-review

quality-review

bug-blitz

bugfix