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/code-review)<a href="https://agentmods.dev/commands/lifangda/claude-plugins/code-review"><img src="https://agentmods.dev/badge/commands/lifangda/claude-plugins/code-review/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/code-review"><img src="https://agentmods.dev/badge/commands/lifangda/claude-plugins/code-review.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.00008 | $0.00176 |
| Opus 5.5 | $0.00003 | $0.00070 |
| Sonnet 5.5 | $0.00002 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
code-review 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 code-review — 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
Context
- Current git status: !
git status - Recent changes: !
git diff HEAD~1 - Recent commits: !
git log --oneline -5 - Current branch: !
git branch --show-current
Your task
Perform a comprehensive code review focusing on:
- Code Quality: Check for readability, maintainability, and adherence to best practices
- Security: Look for potential vulnerabilities or security issues
- Performance: Identify potential performance bottlenecks
- Testing: Assess test coverage and quality
- Documentation: Check if code is properly documented
Provide specific, actionable feedback with line-by-line comments where appropriate.
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 · 23 lines · 8 tokens per session scan A 6733b9e528e6
code-review is a command published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 11mo ago), licensed MIT. It adds 8 tokens to every session and 176 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to code-review, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.