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/hekmon8/awesome-claude-code-plugins/reviewgit clone --depth 1 https://github.com/hekmon8/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/hekmon8/awesome-claude-code-plugins/review)<a href="https://agentmods.dev/commands/hekmon8/awesome-claude-code-plugins/review"><img src="https://agentmods.dev/badge/commands/hekmon8/awesome-claude-code-plugins/review.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.00000 | $0.00458 |
| Opus 5 | $0.00000 | $0.00229 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Command
Perform a comprehensive code review of recent changes.
Review Checklist
1. Code Quality
- Readability: Is the code easy to understand?
- Maintainability: Can future developers easily modify this?
- DRY Principle: Is there duplicated code that should be extracted?
- Naming: Are variables, functions, and classes well-named?
2. Functionality
- Logic Errors: Are there any logical mistakes?
- Edge Cases: Are edge cases handled properly?
- Error Handling: Is error handling comprehensive?
- Input Validation: Are inputs properly validated?
3. Performance
- Algorithmic Efficiency: Could algorithms be more efficient?
- Resource Usage: Is memory and CPU usage optimal?
- Database Queries: Are queries optimized (N+1 problems)?
- Caching: Should caching be implemented?
4. Security
- SQL Injection: Are queries parameterized?
- XSS: Is user input sanitized?
- Authentication: Is authentication properly implemented?
- Authorization: Are permissions checked correctly?
- Secrets: Are there any exposed secrets or credentials?
5. Testing
- Test Coverage: Are new features tested?
- Test Quality: Are tests meaningful and thorough?
- Edge Cases: Are edge cases tested?
6. Documentation
- Code Comments: Complex logic explained?
- API Documentation: Public APIs documented?
- README Updates: Documentation updated?
Output Format
Provide your review in this structure:
# Code Review Report
## ✅ Strengths
[List positive aspects of the code]
## ⚠️ Issues Found
### High Priority
[Critical issues that must be fixed]
### Medium Priority
[Important issues that should be addressed]
### Low Priority
[Nice-to-have improvements]
## 🔧 Specific Recommendations
1. [Actionable recommendation with file:line reference]
2. [Actionable recommendation with file:line reference]
## 📊 Summary
[Brief overall assessment]
Be constructive, specific, and include file:line references for all issues.
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 · 72 lines · 0 tokens per session scan A a918fdb6f89e
review is a command published in the GitHub repository hekmon8/awesome-claude-code-plugins (5 stars, last pushed 10mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 458 tokens. 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.