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 skills add fall-out-bug/sdp --skill bugfixgit 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/skills/fall-out-bug/sdp/bugfix)<a href="https://agentmods.dev/skills/fall-out-bug/sdp/bugfix"><img src="https://agentmods.dev/badge/skills/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/skills/fall-out-bug/sdp/bugfix"><img src="https://agentmods.dev/badge/skills/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.00027 | $0.00702 |
| Opus 5.5 | $0.00011 | $0.00281 |
| Sonnet 5.5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@bugfix
Quality bug fixes with full TDD cycle. Branch from master via feature/.
When to Use
- P1 (HIGH) or P2 (MEDIUM) issues
- Feature broken but not production
- Reproducible errors
Workflow
- Read issue —
bd show <id>or load fromdocs/issues/ - Branch —
git checkout master && git pull && git checkout -b fix/{id}-{slug} - TDD — Red: failing test → Green: minimal fix → Refactor
- Quality gates — Run quality gates (see Quality Gates in AGENTS.md)
- Commit —
git commit -m "fix(scope): description" - Push —
git push -u origin fix/{branch}thengh pr create --base master
Write Plan (F101)
Before modifying any file, emit a write plan:
- Enumerate — List every file the skill will CREATE / MODIFY / DELETE with a one-line reason (test files and fix files).
- Flags:
--dry-run— Emit write plan only. Do NOT create, modify, or delete any file.--yes— Skip confirmation prompt. Execute immediately. Intended for CI/non-interactive.
- Confirm — Present the plan to the user and wait for explicit approval (unless
--yes). - Log — Append write plan event to
.sdp/log/events.jsonl(sanitize file paths before logging: strip newlines, ensure valid JSON escaping):
Include context fields only when the ID is known at plan time. Omit unavailable fields rather than inventing placeholders.{"spec_version":"v1.0","event_id":"<uuid>","timestamp":"<ISO-8601>","source":{"system":"sdp-lab","component":"bugfix"},"event_type":"decision.made","payload":{"decision_type":"write_plan","plan":[{"path":"...","action":"CREATE|MODIFY|DELETE","reason":"..."}]},"context":{"feature_id":"<F-id if known>","workstream_id":"<ws-id if applicable>"}}Note: Phase 1 uses prompt-level write boundaries (CLI out of scope). Aligns with
sdp/schema/contracts/orchestration-event.schema.jsonviaevent_type: "decision.made". Phase 2 CLI will emit natively.
Output format:
WRITE PLAN for @bugfix <target>:
CREATE: path/to/new/file — <reason>
MODIFY: path/to/existing/file — <reason>
DELETE: path/to/removed/file — <reason>
Proceed? [y/n]
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 · 65 lines · 27 tokens per session scan A 60ae8a30c851
bugfix is a skill published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 702 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 skills, from other repositories
polya-fix
Phase 5 of the Pólya Heuristic Coder: First-Principles Bug Remediation, Seam Tracing, Bisection Search (O(log n)), Failing Reproduction Tests, and Incubation Circuit-Breaker Gate (docs/bug-reports/{slug}-bugfix.md).
bugfix-quick
Fast bug fixes with root cause investigation + TDD. Enforces 'no fix without root cause' discipline and verification protocol. Without this skill, fixes are applied at symptoms instead of sources, and bugs return.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
mushi-integration
Full end-to-end Mushi Mushi integration smoke test: bug capture → AI triage → story mapping → TDD test generation → approval → execution → PDCA cycle. Use when "test mushi integration", "verify full pipeline", "mushi e2e check", "does mushi work end-to-end", "smoke test mushi", or after deploying changes.
tdd-bug-report
Workflow for analyzing bug reports, tracing root causes, and generating structured bug-fix implementation plans enforcing the Prove-It pattern (failing regression test first) with rollback strategies.
regression-test
Classify an iOS/Swift bug into its Apple-specific root-cause class (force unwrap, try!, fatalError, MainActor isolation, App Group mismatch, lifecycle) and sweep for sibling instances of that class. Complements a generic TDD/debugging skill (e.g. superpowers:test-driven-development, superpowers:systematic-debugging)…