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/ccplugins/awesome-claude-code-plugins/bug-fixgit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWrote 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/ccplugins/awesome-claude-code-plugins/bug-fix)<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/bug-fix"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/bug-fix.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.00026 | $0.00136 |
| Opus 5 | $0.00013 | $0.00068 |
| Sonnet 5 | $0.00005 | $0.00027 |
| Haiku 4.5 | $0.00003 | $0.00014 |
Grade A, and why
bug-fix 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 today.
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.
What it actually says
Understand the bug: $ARG
Before Starting:
- GITHUB: create a issue with the a short descriptive title.
- GIT: checkout a branch and switch to it.
Fix the Bug
On Completion:
- GIT: commit with a descriptive message.
- GIT: push the branch to the remote repository.
- GITHUB: create a PR and link the issue.
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.
- today First seen · 19 lines · 26 tokens per session scan A dd94b2db1d5a
bug-fix is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (931 stars, last pushed 22d ago), licensed Apache-2.0. It adds 26 tokens to every session and 136 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-03.
Other commands, from other repositories
claude-desktop-extension
This command provides the context necessary for Claude Code to create the Desktop Extension or .dxt file of an MCP.
clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
new-sdk-app
Create and setup a new Claude Agent SDK application.
analyze-codebase
Generate comprehensive analysis and documentation of entire codebase.
analyze-issue
Fetches GitHub issue details to create comprehensive implementation specifications, analyzing requirements and planning structured approach with clear implementation steps.
audit
Perform security audit on codebase.