Borrowing it
Nothing to install: this file belongs to rshade/mcp-devtools-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rshade/mcp-devtools-server/main/.claude/commands/review-pr.mdgit clone --depth 1 https://github.com/rshade/mcp-devtools-serverWrote 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/rshade/mcp-devtools-server/review-pr)<a href="https://agentmods.dev/commands/rshade/mcp-devtools-server/review-pr"><img src="https://agentmods.dev/badge/commands/rshade/mcp-devtools-server/review-pr/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/rshade/mcp-devtools-server/review-pr"><img src="https://agentmods.dev/badge/commands/rshade/mcp-devtools-server/review-pr.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.00000 | $0.00448 |
| Opus 5.5 | $0.00000 | $0.00179 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
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 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.
What it actually says
Launch the Code Review and Fix Agent (Sonnet) to perform comprehensive code review.
Usage: /review-pr [pr-number] [--fix]
Options:
- pr-number: PR number to review (required)
- --fix: Automatically implement fixes for critical issues
Example: /review-pr 42 Example: /review-pr 42 --fix
Launch Code Review Agent with Sonnet model for deep analysis.
Use the Task tool with:
- subagent_type: general-purpose
- model: sonnet
- prompt: Follow the Code Review and Fix Agent guide
Task:
You are the Code Review and Fix Agent. Follow .claude/agents/code-review-fix.md to:
-
Gather context (10-15 min):
gh pr view {{PR_NUMBER}} --repo rshade/mcp-devtools-server --json title,body,files gh pr diff {{PR_NUMBER}} --repo rshade/mcp-devtools-server gh pr checks {{PR_NUMBER}} --repo rshade/mcp-devtools-server -
Deep analysis (20-30 min):
- Review across 5 dimensions (correctness, security, performance, maintainability, best practices)
- Read all changed files
- Check test coverage
- Verify quality gates
-
Prioritize issues:
- Critical (security, data loss)
- High (performance, missing features)
- Medium (duplication, docs)
- Low (cosmetic)
-
Generate comprehensive review:
- Issue breakdown by severity
- Specific line-by-line feedback
- Fix recommendations
- Test coverage analysis
- Overall assessment
{{#if FIX}} 5. Implement fixes (if --fix flag):
- Fix critical issues
- Add missing tests
- Run quality gates
- Generate fix summary {{/if}}
Success criteria:
- All files analyzed
- Issues categorized
- Critical issues documented/fixed
- Test coverage verified (85%+)
- Quality gates pass (if fixing)
Return comprehensive review with severity-based 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.
- 1mo ago First seen · 67 lines · 0 tokens per session scan A c95a0fb67e51
review-pr is a command published in the GitHub repository rshade/mcp-devtools-server (5 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 448 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
sw-audit
Periodic codebase health check for systemic technical debt.
sw-review
PR comment review. Group by status and respond inline.
review-artifact-comments
Works through the review comments written into a task artifact (plan or research under .ork/tasks/TASK/): lists the open ones, asks how to proceed, then replies, resolves or hands off to iterate-plan or iterate-research, and approves the artifact once nothing is open. Use when a reviewer has commented on an artifact…
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.