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/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/code-review-assistant)<a href="https://agentmods.dev/commands/ccplugins/awesome-claude-code-plugins/code-review-assistant"><img src="https://agentmods.dev/badge/commands/ccplugins/awesome-claude-code-plugins/code-review-assistant.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.1 | $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 3d 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
2 near-identical copies found in the catalogue:
- code-review-assistant — 100% identical, 0 lines differ
- 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.
- 3d ago First seen · 22 lines · 7 tokens per session scan A 1de81c7d0c92
code-review-assistant is a command published in the GitHub repository ccplugins/awesome-claude-code-plugins (932 stars, last pushed 25d ago), licensed Apache-2.0. 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-09-03.
Other commands, from other repositories
code-review-assistant
Comprehensive code review with improvement suggestions.
pr-issue-resolve
Follow these steps to analyze suggested changes (e.g., review comments, inline suggestions, or requested modifications) in a GitHub Pull Request (PR) and resolve them efficiently. The goal is to review, understand, plan fixes, apply changes, test, and update the PR while maintaining code quality and collaboration.
pr-review
Reviews pull request changes to provide feedback, check for issues, and suggest improvements before merging into the main codebase.
husky
Sets up and manages Husky Git hooks by configuring pre-commit hooks, establishing commit message standards, integrating with linting tools, and ensuring code quality on commits.
refractor
Refactor code following best practices and design patterns.
fix-pr
Fetches and fixes unresolved PR comments by automatically retrieving feedback, addressing reviewer concerns, making targeted code improvements, and streamlining the review process.