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/Habib0x0/spec-driven-pluginWrote 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/habib0x0/spec-driven-plugin/spec-bugfix)<a href="https://agentmods.dev/commands/habib0x0/spec-driven-plugin/spec-bugfix"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-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/habib0x0/spec-driven-plugin/spec-bugfix"><img src="https://agentmods.dev/badge/commands/habib0x0/spec-driven-plugin/spec-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.00020 | $0.00561 |
| Opus 5.5 | $0.00008 | $0.00224 |
| Sonnet 5.5 | $0.00004 | $0.00112 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
spec-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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-bugfix Command
Guide a bugfix through a three-phase workflow: Bug Analysis, Design, and Tasks.
Unlike feature specs which start from requirements, bugfix specs start from a documented defect and work toward a surgical fix with regression prevention.
Usage
/spec-bugfix <bug-name>
Arguments
| Argument | Required | Description |
|---|---|---|
bug-name |
Yes | A short, kebab-case identifier for the bugfix. Used as the directory name. |
Workflow
Phase 1: Bug Analysis
The agent guides the user through documenting the defect:
- Current Behavior (Defect) —
WHEN [condition] THEN the system [incorrect behavior] - Expected Behavior (Correct) —
WHEN [condition] THEN the system SHALL [correct behavior] - Unchanged Behavior (Regression Prevention) —
WHEN [condition] THEN the system SHALL CONTINUE TO [existing behavior] - Reproduction Steps — exact steps to reproduce the defect
- Constraints — code that must not be modified, backward-compat requirements, etc.
The agent also performs automated root cause analysis by exploring the codebase around the defect.
Output: bugfix.md
Phase 2: Design
The agent proposes a fix approach:
- Root cause summary
- Proposed fix with minimal blast radius
- Test properties to verify (reproducible, fixed, no regression)
- Risk assessment
Output: design.md
Phase 3: Tasks
The agent breaks the fix into discrete tasks:
- Reproduction test (confirms the bug exists)
- Fix implementation (surgical change)
- Regression tests (verify unchanged behavior still works)
- Validation (confirm all three test properties pass)
Output: tasks.md
Directory Structure
.claude/specs/<bug-name>/
bugfix.md # Bug analysis with current/expected/unchanged behavior
design.md # Fix approach and test properties
tasks.md # Discrete implementation tasks
Tips
- Be explicit about what code must NOT change — constraints prevent over-fixing
- Document unchanged behavior carefully — this is what prevents regressions
- The reproduction test should fail before the fix and pass after
- Keep the fix surgical; resist the urge to refactor surrounding code
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 · 85 lines · 20 tokens per session scan A 70b18026f302
spec-bugfix is a command published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 561 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-31.
Other commands, from other repositories
validate-consistency
Cross-command consistency validator — detects conflicts between outputs from different /architect: commands.
check-state
Validate project state consistency — schema compliance, type checking, per-command write rule violations.
sdl-drift
Detect architecture drift — compare current codebase against committed SDL and surface topology changes.
orient-trace
Trace one execution path — entry point to edges — with file:line refs.
analyze
Analyze a .NET project or solution — list projects, check diagnostics, and present a structured summary.
sruja-bugfix-triage
Systematic workflow for triaging and fixing bugs with architecture grounding.