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.
git clone --depth 1 https://github.com/fall-out-bug/sdpWrote 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/commands/fall-out-bug/sdp/bugfix)<a href="https://agentmods.dev/commands/fall-out-bug/sdp/bugfix"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/bugfix/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/commands/fall-out-bug/sdp/bugfix"><img src="https://agentmods.dev/badge/commands/fall-out-bug/sdp/bugfix.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.00017 | $0.00289 |
| Opus 5.5 | $0.00007 | $0.00116 |
| Sonnet 5.5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
bugfix 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.
What it actually says
/bugfix — Quality Bug Fixes
When calling /bugfix issue NNN:
- Read issue — Load
docs/issues/{NNN}-*.md - Create branch —
git checkout -b bugfix/{NNN}-{slug}from master - TDD cycle — Write failing test → implement fix → refactor
- Quality gates — run quality gates (see AGENTS.md)
- Commit —
fix(scope): description (issue NNN) - Mark issue closed — Update status in issue file
- MERGE AND PUSH — Execute yourself, not instructions!
CRITICAL: You MUST Complete
git checkout master
git merge bugfix/{branch} --no-edit
git push
git status # MUST show "up to date with origin"
Work is NOT complete until git push succeeds.
Quick Reference
Input: P1/P2 issue
Output: Bug fixed + tests + pushed to origin
| Aspect | Hotfix | Bugfix |
|---|---|---|
| Severity | P0 | P1/P2 |
| Branch from | master | master |
| Testing | Fast | Full |
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 · 39 lines · 17 tokens per session scan A fb871000c7d8
bugfix is a command published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 289 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.
Other commands, from other repositories
refactor
You are the Refactor Specialist, a rigorous code quality engineer who improves code structure, maintainability, and performance while preserving behavior. You never break working code - you make it better.
tdd-bug
Fix a bug with regression test first.
fix
Use for a fast bug fix with minimal ceremony (3 questions, TDD, done).
spec-impl
Execute spec tasks using TDD methodology.
api-aqa-flow
Workflow for backend API test automation: TMS / Issue Tracker test cases → automated API tests, HITL-gated.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.