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 agentmods add commands/olehsvyrydov/ai-development-team/buggit clone --depth 1 https://github.com/olehsvyrydov/AI-development-teamWhat 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.00019 | $0.00894 |
| Opus 5 | $0.00010 | $0.00447 |
| Sonnet 5 | $0.00004 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
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 3d 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 — 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 |
+-------------------------+
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.
- 3d ago First seen · 150 lines · 19 tokens per session scan A 5ce1cff84a95
bug is a command published in the GitHub repository olehsvyrydov/AI-development-team (16 stars, last pushed 24d ago), licensed MIT. It adds 19 tokens to every session and 894 once invoked, about $0.0001 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.
Other commands, from other repositories
loop
Iteratively fix issues until all resolved or max iterations reached.
quality-gate
Command "quality-gate" from VoDaiLocz/kilo-kit-mcp, covering ✅ quality gate command, workflow, gates, gate 1: pre-execution and gate 2: per-behavior.
deep-audit.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Ornek cikti.
do-it-retrospective
开关本项目的本地行为反馈记录，或输出已记录问题的去敏复盘报告。参数为 on / off / status / report。.
fix-issue
!gh issue view $ARGUMENTS 2>/dev/null || echo "Could not fetch issue $ARGUMENTS".
verify
Verify factual claims in content using deep research methodology - fact-checks key assertions and updates NCI scores.