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/mshadmanrahman/pm-pilotWrote 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/mshadmanrahman/pm-pilot/code-review)<a href="https://agentmods.dev/commands/mshadmanrahman/pm-pilot/code-review"><img src="https://agentmods.dev/badge/commands/mshadmanrahman/pm-pilot/code-review/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/mshadmanrahman/pm-pilot/code-review"><img src="https://agentmods.dev/badge/commands/mshadmanrahman/pm-pilot/code-review.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.00014 | $0.00105 |
| Opus 5.5 | $0.00006 | $0.00042 |
| Sonnet 5.5 | $0.00003 | $0.00021 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
code-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 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
/code-review
Review recent code changes for quality, security, and maintainability.
Usage
/code-review {optional: specific files or PR}
Behavior
- Invoke the code-reviewer agent from
agents/code-reviewer.md - Analyze all staged/recent changes
- Report CRITICAL, HIGH, MEDIUM issues
- Block commit on CRITICAL 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.
- 1mo ago First seen · 19 lines · 14 tokens per session scan A e7932478acda
code-review is a command published in the GitHub repository mshadmanrahman/pm-pilot (22 stars, last pushed 17d ago), licensed MIT. It adds 14 tokens to every session and 105 once invoked, about $0.0001 per session on Opus 5.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-08-30.
Other commands, from other repositories
qa-loop
Autonomous loop AUDIT (parallel) → VALIDATE → FIX → VERIFY → CHECK with stopping criteria.
qa-review
Performs a thorough and constructive code review.
work-pr
Creates a complete and well-documented Pull Request.
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.