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/dinhnguyenngoc/spec-driven-claude-code/fix-issuegit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWhat 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.00013 | $0.02826 |
| Opus 5 | $0.00006 | $0.01413 |
| Sonnet 5 | $0.00003 | $0.00565 |
| Haiku 4.5 | $0.00001 | $0.00283 |
Grade A, and why
fix-issue 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 yesterday.
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 — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fix-issue — Bug Fix
"Fix root causes, not symptoms."
Purpose
Analyze and fix a reported bug or issue systematically. This command handles issues from external sources (QA, production, users, issue trackers).
Workspace Mode: if the session root declares
Mode: workspace→ resolve the target repo perCLAUDE.md§Workspace Mode before anything else; every path, probe, and gate below is relative to the target repo, and the workspace disk-check applies at the gate.
Stack Profile note: the
dotnetcommands and C# examples below use the default profile. Core = Node.js → map to the npm equivalents (npm test,tsc --noEmit,npm run build; debug tooling per the declared stack) — the Common Issue Patterns are default-stack illustration only (rules/overrides/lang-nodejs.mdidioms apply). Core = PHP →php artisan test/vendor/bin/pestfor the suite,vendor/bin/pint --test+vendor/bin/phpstan analysefor the format/analyzer steps (rules/overrides/lang-php.md+test-php.mdidioms apply).
When to Use
| Situation | Command |
|---|---|
| Bug report from QA/Production/Users | → /fix-issue |
| Jira/Linear ticket or issue tracker | → /fix-issue |
BUG-### filed in reports/TEST_REPORT.md §8, or a failure in reports/VERIFY_REPORT.md §3 |
→ /fix-issue |
/build or /test fails unexpectedly |
→ /debug |
| Error occurs during development | → /debug |
Usage
/fix-issue JIRA-456 # Fix Jira ticket
/fix-issue LIN-123 # Fix Linear ticket
/fix-issue "Users cannot login" # Fix bug from description
Process
1. Understand the Issue
- Read the error message or bug description carefully
- Identify the affected component(s)
- Reproduce the issue locally if possible
Expected behavior must have a source — ambiguity in a fix is a spec question. If the expected behavior cannot be derived from
specs/, existing tests, or the bug report — i.e. there is no test oracle: no authoritative answer to "what is correct here?" — treat it as blocking: stop and ask before writing the fix (perprinciples-and-practices.md§2.5); a wrong guess here ships fast. Implementation details follow the standard ladder; any non-blocking behavior assumption you do make is recorded asA-xxin the commit body + completion summary for review.
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.
- yesterday First seen · 271 lines · 13 tokens per session scan A 749b048a440b
fix-issue is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (20 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 2,826 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
spec-kitty.analyze
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
my-own-prompt
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
sdd-lifecycle
Spec status, moves between backlog/active/done, plan archiving at completion.
assign
Turn a backlog item (ID-NNN) into a scoped goal draft and route it into the right WORKFLOW lane. Writes .claude/goals/, never executes.
sdd-overview
Workflow overview, current spec status, and the SDD command list.
retro
Run a retrospective after shipping. Captures what worked, what didn't, and action items for the next cycle. Outputs to docs/retro/RETRO.md.