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/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/plan-bugfix)<a href="https://agentmods.dev/commands/alexgvozden/claude-plugin/plan-bugfix"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/plan-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/alexgvozden/claude-plugin/plan-bugfix"><img src="https://agentmods.dev/badge/commands/alexgvozden/claude-plugin/plan-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.00011 | $0.01852 |
| Opus 5.5 | $0.00004 | $0.00741 |
| Sonnet 5.5 | $0.00002 | $0.00370 |
| Haiku 4.5 | $0.00001 | $0.00185 |
Grade A, and why
plan-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 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: PLANNING ONLY - NO CODE IMPLEMENTATION
This command is exclusively for PLANNING bug fixes. Do NOT:
- Write any code
- Create or modify components
- Install dependencies
- Run any bash commands
- Make any changes to the codebase
ONLY:
- Read existing files to understand context
- Create or update bug fix planning documentation in the planning/bugs/ folder
- Ask clarifying questions about the bug if details are unclear
- Analyze potential root causes
You are tasked with planning a bug fix following the workflow outlined in CLAUDE.md.
Instructions
-
Understand the Bug:
- If a planning file path is provided (e.g., planning/bugs/KT-4313-fix-displaying-employee-data-for-august-healthcare.md), read it to understand the existing plan
- If no file is provided or it doesn't exist, this is a new bug - gather information from the user's description
- ASK CLARIFYING QUESTIONS if the bug description is unclear or missing critical information:
- What is the expected behavior?
- What is the actual behavior?
- When did this bug start occurring?
- Are there any error messages or logs?
- What are the steps to reproduce?
- Which users/data are affected?
- Is this a regression or existing issue?
-
Follow CLAUDE.md Guidelines:
- Review CLAUDE.md for project structure and guidelines
- Ensure the plan respects:
- Project best practices and conventions
- Existing database patterns
- Styling conventions
- Existing component patterns
- Naming conventions
- API endpoint documentation requirements
-
Create Comprehensive Bug Fix Plan:
Structure the plan with these sections:
Bug: [Bug Title with KT-XXXX prefix]
Bug Summary
- Ticket ID: KT-XXXX
- Severity: Critical / High / Medium / Low
- Affected Components: List of affected files, components, or features
- Reported Date: When the bug was discovered
- Reporter: Who reported it (if applicable)
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 · 234 lines · 11 tokens per session scan A 3a8764364aba
plan-bugfix is a command published in the GitHub repository alexgvozden/claude-plugin (11 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 1,852 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.
plan-bugfix compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| plan-bugfixalexgvozden/claude-plugin | Command | 11 | 11mo ago | MIT | A | 11 | 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 |