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/rshade/mcp-devtools-server/review-prgit 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.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.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 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 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.
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.
- 3d 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 4d 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-init
Project setup. Creates constitution and charter. Configures gates.
sw-doctor
Read-only installation health check with repair hints.
sw-guard
Detect stack and configure deterministic guardrails.
sw-status
Show current Specwright state and progress.
sw-pivot
Research-backed rebaselining for planning, building, or verifying work. Preserves completed and shipped scope while revising remaining design, plan, and in-progress work.
sw-ship
Strategy-aware merge via pull request. If branch-head freshness blocks and policy is rebase or merge, recover in the same run; manual is the fallback and still reruns /sw-verify before /sw-ship.