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 skills add thebtf/pr-review-mcp --skill pr-reviewgit clone --depth 1 https://github.com/thebtf/pr-review-mcpWrote 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/skills/thebtf/pr-review-mcp/pr-review)<a href="https://agentmods.dev/skills/thebtf/pr-review-mcp/pr-review"><img src="https://agentmods.dev/badge/skills/thebtf/pr-review-mcp/pr-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/skills/thebtf/pr-review-mcp/pr-review"><img src="https://agentmods.dev/badge/skills/thebtf/pr-review-mcp/pr-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.00042 | $0.00654 |
| Opus 5 | $0.00021 | $0.00327 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
pr-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 10d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pr-review
Use this as the canonical consumer-facing entry for PR review workflows.
TL;DR
pr-revieweris the built-in background autonomous executor agent.- This skill is the canonical consumer-facing entry for dispatching that agent.
/pr:reviewremains the built-in MCP prompt slash command for MCP-native flows and compatibility, but it is not the primary plugin workflow surface.
Interface boundaries (must stay explicit)
- MCP tools:
mcp__pr__pr_*(data/actions: summary, list, get, invoke, await, resolve, etc.) - MCP prompts / slash commands:
/pr:review,/pr:review-background,/pr:setup - Claude skills: this file (
skills/pr-review/SKILL.md) and otherSKILL.mdartifacts
Core workflow
- Parse input PR target (number,
owner/repo#N, or URL). - Dispatch the built-in
pr-revieweragent in background (model: sonnet). - Let
pr-reviewerrun the full MCP-native review cycle:- invoke reviewers (
pr_invoke) - await completion (
pr_await_reviews/pr_poll_updates) - process findings (
pr_list,pr_get, code fixes) - prefer
mcp__aimux__agentsfor larger code changes when aimux is available in the consumer environment - otherwise apply fixes locally through the shipped MCP/tool surface
- resolve fixed threads (
pr_resolve) - hand back structured readiness report
- invoke reviewers (
- Keep merge decision outside the worker (never auto-merge).
- Use
/pr:reviewonly when you explicitly want the MCP prompt/slash-command path instead of the built-in plugin agent path.
Non-negotiable review rules
- Process all severities, including MINOR and NITPICK.
- Confidence-check every suggestion before applying.
- Resolve each fixed thread.
- Hand back with explicit status: READY_FOR_HUMAN_MERGE | NEEDS_USER_DECISION | BLOCKED.
Anti-patterns
Skill("mcp__pr__review")— wrong abstraction. That is not a Claude skill.- Treating
/pr:reviewas the only plugin-facing interface — wrong. The built-inpr-revieweragent is the primary plugin workflow surface. - Manual main-context review via
gh pr diff/gh api ...commentsas primary review path — wrong. Use the built-in agent or MCP-native prompt/tool flow. - Auto-merging from autonomous worker — forbidden.
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.
- 10d ago First seen · 52 lines · 42 tokens per session scan A 2b720a648eb7
pr-review is a skill published in the GitHub repository thebtf/pr-review-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 654 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…