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/lifangda/claude-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/lifangda/claude-plugins/bug-fix)<a href="https://agentmods.dev/commands/lifangda/claude-plugins/bug-fix"><img src="https://agentmods.dev/badge/commands/lifangda/claude-plugins/bug-fix/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/lifangda/claude-plugins/bug-fix"><img src="https://agentmods.dev/badge/commands/lifangda/claude-plugins/bug-fix.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.00026 | $0.00136 |
| Opus 5.5 | $0.00010 | $0.00054 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to bug-fix — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 19 lines · 26 tokens per session scan A dd94b2db1d5a
bug-fix is a command published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 11mo ago), licensed MIT. It adds 26 tokens to every session and 136 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to bug-fix, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
barista-fix
Attempt a small, focused fix for a frappe-ui issue and open a draft PR.
fix-issue
Fixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to…
unbloat
Remove dead code, duplicate files, and unused dependencies with user approval at each step. Backs up before deleting.
payload-revert
Stage reverts for high-confidence payload candidates identified by payload-analysis.
AGENTS
Run the current binary in a temporary test repository with a real PTY. Use tmux-cli when available, capture terminal output, and inspect -vv logs when behavior depends on timing or shell state. Avoid treating a piped command as proof of interactive behavior.
fix-issue
Analyze and fix the GitHub issue: $ARGUMENTS.