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/lifangda/claude-plugins/code-review-assistantgit clone --depth 1 https://github.com/lifangda/claude-pluginsWhat 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.00007 | $0.00161 |
| Opus 5 | $0.00003 | $0.00081 |
| Sonnet 5 | $0.00001 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
code-review-assistant 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- code-review-assistant — 100% identical, 0 lines differ
What it actually says
Code Review Assistant
You are an expert code reviewer. Please review the provided code and give detailed feedback on:
- Code Quality: Readability, maintainability, and adherence to best practices
- Performance: Potential bottlenecks and optimization opportunities
- Security: Vulnerabilities and security concerns
- Architecture: Design patterns and architectural improvements
- Testing: Test coverage and testing strategy recommendations
Please provide:
- Specific line-by-line comments where applicable
- Overall assessment and rating (1-10)
- Priority-ordered list of improvements
- Positive aspects worth highlighting
Format your response with clear sections and actionable recommendations.
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.
- 2d ago First seen · 22 lines · 7 tokens per session scan A 1de81c7d0c92
code-review-assistant is a command published in the GitHub repository lifangda/claude-plugins (43 stars, last pushed 10mo ago), licensed MIT. It adds 7 tokens to every session and 161 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
five
Apply the Five Whys root cause analysis technique to investigate an issue.
safe-refactor
Safe refactoring with automated review, testing, and rollback capabilities.
test
Smart test runner with filtering, coverage, and health monitoring.
vd-arch-review
Audita arquitetura de código em 3 níveis (macro/meso/micro). Detecta separação de camadas, anti-patterns, vazamento de abstração, dependências externas vs código customizado, acoplamento. User-invoked, sob demanda, para devs (não leigo). Use quando o usuário pede "auditoria arquitetural", "code review arquitetural"…
vd-manual
Rodado automaticamente dentro do /vd-close (opt-out via flag --no-manual).
vibeshield-code-review
Review a code diff or PR against two axes: Standards (does the code follow VibeDev conventions?) and Spec (does it implement what the spec said?). Returns a list of findings with severity, axis, and suggested fix.