Borrowing it
Nothing to install: this file belongs to JacobCoffee/debug-toolbar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JacobCoffee/debug-toolbar/main/.claude/commands/fix-issue.mdgit clone --depth 1 https://github.com/JacobCoffee/debug-toolbarWrote 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/jacobcoffee/debug-toolbar/fix-issue)<a href="https://agentmods.dev/commands/jacobcoffee/debug-toolbar/fix-issue"><img src="https://agentmods.dev/badge/commands/jacobcoffee/debug-toolbar/fix-issue.svg" alt="Measured on agentmods" 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.00010 | $0.00650 |
| Opus 5 | $0.00005 | $0.00325 |
| Sonnet 5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix GitHub Issue
You are fixing issue: $ARGUMENTS
Workflow
Phase 1: Issue Analysis
Fetch issue details:
gh issue view {issue_number}
Understand the issue:
- What is the problem?
- What is the expected behavior?
- What is the actual behavior?
- Can it be reproduced?
Output: "✓ Phase 1 complete - Issue understood"
Phase 2: Root Cause Investigation
Use debug tools:
mcp__zen__debug(
step="Investigating issue #{issue_number}",
step_number=1,
total_steps=3,
next_step_required=True,
findings="Initial investigation..."
)
Search codebase:
# Find related code
grep -r "{keyword}" src/
# Find related tests
grep -r "{keyword}" tests/
Output: "✓ Phase 2 complete - Root cause identified"
Phase 3: Fix Implementation
Follow existing patterns:
- Read similar fixes in git history
- Follow code style from
CLAUDE.md - Maintain type safety
Implement fix:
- Make minimal necessary changes
- Don't over-engineer
- Add or update tests
Output: "✓ Phase 3 complete - Fix implemented"
Phase 4: Testing
Write test for the fix:
"""Test for issue #{issue_number} fix."""
from __future__ import annotations
import pytest
class TestIssueNumber:
"""Test that issue #{issue_number} is fixed."""
def test_issue_scenario(self) -> None:
"""Should not exhibit the bug behavior."""
# Arrange: Set up the scenario from the issue
# Act: Perform the action that caused the bug
# Assert: Verify the fix works
Run tests:
make test
Output: "✓ Phase 4 complete - Tests passing"
Phase 5: Quality Verification
Run quality gates:
make lint
make type-check
make fmt-check
Output: "✓ Phase 5 complete - Quality gates passed"
Phase 6: Commit
Create commit with issue reference:
git add -A
git commit -m "fix: description of fix
Fixes #{issue_number}"
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 · 159 lines · 10 tokens per session scan A c3c8575f81a4
fix-issue is a command published in the GitHub repository JacobCoffee/debug-toolbar (7 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 650 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-09-04.
Other commands, from other repositories
bug-fix
Systematic workflow for fixing bugs including issue creation, branch management, and PR submission.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
gsd:audit-fix
Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
dev
Developer tools — debug, commit, PR, code review, refactoring.
fix
Quick bugfix commit. Use for fix bug, bugfix, patch, hotfix, correct error.