A command that applies a documented fix for one software bug. It requires the path to a Markdown bug report containing the issue, expected and actual behavior, reproduction details or cause, and a proposed solution.

Use it to validate a bug report, extract the affected files and root cause, create a fix plan, and carry out the specified correction.

It checks that the report has enough information before making a focused fix, which avoids implementing an unclear or incomplete request.

fix-bug — Command for Claude Code by alexgvozden/claude-plugin

Install

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.

Clone the repo

git clone --depth 1 https://github.com/alexgvozden/claude-plugin

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/fix-bug/github.svg)](https://agentmods.dev/commands/alexgvozden/claude-plugin/fix-bug)

Your own site

<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/fix-bug"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/fix-bug/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,492 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.01492
Opus 5.5	$0.00004	$0.00597
Sonnet 5.5	$0.00002	$0.00298
Haiku 4.5	$0.00001	$0.00149

Measured 2mo ago against content hash d4a265ee2b28, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

commands/fix-bug.md · 235 lines

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.

Read the full file on GitHub · 235 lines

Changes

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.

2mo ago First seen · 235 lines · 10 tokens per session scan A d4a265ee2b28

Subscribe to this mod's changes

fix-bug is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 11mo ago), licensed MIT. It adds 10 tokens to every session and 1,492 once invoked, about $0.0000 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.

Debugging

fix-bug next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
fix-bugalexgvozden/claude-plugin	Command	11	11mo ago	MIT	A	10	Claude Code
qa-changesOpenHands/extensions	Command	176	yesterday	MIT	A	63	Claude Code
react-nativegetsentry/toolkit	Command	958	today	none	A	0	Claude Code
auditar-cascadingluanpdd/kit-mcp	Command	5	5d ago	MIT	A	54	Claude Code
http-serviceMadAppGang/magus	Command	14	yesterday	MIT	A	27	Claude Code
doctordoncheli/don-cheli-sdd	Command	59	2mo ago	Apache-2.0	A	76	Claude Code
doctorfatihkan/badi	Command	7	1mo ago	MIT	A	0	Claude Code