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/alexgvozden/claude-plugin/fix-buggit clone --depth 1 https://github.com/alexgvozden/claude-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/alexgvozden/claude-plugin/fix-bug)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/fix-bug"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/fix-bug.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 | $0.00010 | $0.01492 |
| Opus 5 | $0.00005 | $0.00746 |
| Sonnet 5 | $0.00002 | $0.00298 |
| Haiku 4.5 | $0.00001 | $0.00149 |
Grade A, and why
fix-bug 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 4d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BUG FIX COMMAND
This command fixes a bug based on a bug report markdown file, with focused execution on the specific issue.
Required Parameter
Bug Report Path: You MUST provide the path to the bug report markdown file.
Example usage:
/fix-bug planning/bug-kt-1234.md
If no file path provided: Return error message "❌ Error: Bug report file path is required. Usage: /fix-bug planning/bug-report.md" and EXIT.
Instructions
1. Validate Bug Report
Read the bug report and verify:
- File exists at the provided path
- Contains required sections:
- Bug Description: Clear description of the issue
- Steps to Reproduce OR Root Cause: How to reproduce or what's causing it
- Expected Behavior: What should happen
- Actual Behavior: What's currently happening
- Proposed Fix OR Solution: How to fix it
If validation fails: Inform user what's missing and EXIT without proceeding.
2. Create Fix Plan
If validation passes, create a concise fix plan:
-
Extract key information:
- Bug ID (if mentioned)
- Affected files/components
- Root cause analysis
- Proposed solution steps
-
Add Fix Progress Tracker to the bug report at the TOP (after title):
## Bug: [Bug Title]
## Fix Progress
| Step | Description | Status | Notes |
|------|-------------|--------|-------|
| 1 | [Step description] | ⏸️ Pending | |
| 2 | [Step description] | ⏸️ Pending | |
| 3 | [Step description] | ⏸️ Pending | |
**Legend**: ✅ Complete | 🔄 In Progress | ⏸️ Pending | ❌ Blocked
---
### Bug Description
[Rest of original content...]
- Present Fix Plan to user:
🐛 Bug Fix Plan Created
Bug: [Bug Title]
Affected: [Files/Components]
Fix Steps:
1. [Step 1 description]
2. [Step 2 description]
3. [Step 3 description]
✅ Progress tracker added to bug report
- Request Confirmation:
Ready to proceed with the fix? (yes/no)
Wait for explicit "yes" or "y" before proceeding. If "no", respond "Fix cancelled." and EXIT.
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.
- 4d ago First seen · 235 lines · 10 tokens per session scan A d4a265ee2b28
fix-bug is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 1,492 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.