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/florianbruniaux/claude-code-plugins/review-prgit clone --depth 1 https://github.com/FlorianBruniaux/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/florianbruniaux/claude-code-plugins/review-pr)<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-plugins/review-pr"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-plugins/review-pr.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.00012 | $0.02124 |
| Opus 5 | $0.00006 | $0.01062 |
| Sonnet 5 | $0.00002 | $0.00425 |
| Haiku 4.5 | $0.00001 | $0.00212 |
Grade A, and why
review-pr 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 yesterday.
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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Pull Request
Perform a comprehensive code review of a pull request.
Instructions
- Get PR information:
gh pr view $ARGUMENTS --json title,body,files,additions,deletions - Review each changed file
- Provide structured feedback
Review Checklist
Code Quality
- Code is readable and well-organized
- Functions are appropriately sized
- No code duplication
- Meaningful variable/function names
Functionality
- Logic is correct
- Edge cases handled
- Error handling is comprehensive
- No obvious bugs
Security
- No hardcoded secrets
- Input validation present
- No injection vulnerabilities
- Authorization checks in place
Testing
- Tests added for new code
- Existing tests still pass
- Edge cases tested
Documentation
- Code is self-documenting or commented
- README updated if needed
- API changes documented
Output Format
## PR Review: #[number] - [title]
### Summary
[1-2 sentence overview]
### Approval Status
[ ] Approved
[ ] Approved with suggestions
[ ] Changes requested
### Findings
#### Critical (Must Fix)
- [ ] [Issue description] - `file:line`
#### Suggestions (Should Consider)
- [ ] [Improvement] - `file:line`
#### Nitpicks (Optional)
- [ ] [Minor suggestion] - `file:line`
### Positive Highlights
- [What's done well]
### Questions
- [Clarifications needed]
Usage
/review-pr 123
/review-pr https://github.com/owner/repo/pull/123
Advanced: Multi-Agent Review
For production-grade reviews requiring specialized perspectives and anti-hallucination safeguards.
Pre-flight Check
Before reviewing, check if this is a follow-up pass to avoid repeating suggestions:
# Detect if Claude already reviewed this PR
git log --oneline -10 | grep "Co-Authored-By: Claude"
If detected, note: "This appears to be a follow-up pass. I'll focus on new issues and avoid repeating previous suggestions."
Scope Drift Detection
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.
- yesterday First seen · 298 lines · 12 tokens per session scan A 4f6520950a6d
review-pr is a command published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 2,124 once invoked, about $0.0001 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-04.
Other commands, from other repositories
content-generate
Social media content generation command. Produces ready-to-use posts, captions, visual briefs, and hashtags for the given platform and type.
api-doc
API documentation generation. Scans route definitions and produces structured API docs.
aso
App Store Optimization command. iOS app listing analysis via the iTunes API, keyword optimization, and competitor comparison.
changelog
Automatic changelog generation. Produces a structured changelog from commit history.
coach
Coaching analysis command. Performs data-driven work-pattern analysis and offers personal improvement suggestions.
competitive-intel
Competitive analysis command. Analyzes the market, competitors, and opportunities with a comprehensive competitive-intelligence framework.