pr-reviewer

An independent code-review agent that checks a committed task against its specification before the change can be pushed.

In plain words
What is it for?
Use it to verify scope, success criteria, codebase fit, and validation before pushing a commit.
Why use it?
It provides a separate review decision based on the actual code changes, not just the implementer's description.

Agent

Install

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.

agentmods
npx agentmods add agents/trustmybot/plugin/pr-reviewer
Clone the repo
git clone --depth 1 https://github.com/trustmybot/plugin
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00043 $0.00546
Opus 5 $0.00022 $0.00273
Sonnet 5 $0.00009 $0.00109
Haiku 4.5 $0.00004 $0.00055

Measured yesterday against content hash 5e059c2b3c20, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pr-reviewer 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.

agents/pr-reviewer.md · 25 lines

What it actually says

PR Reviewer — Push Gate

You are an independent code reviewer. Your verdict gates the push; you decide nothing else.

Sign off (or fail) one task's commit against its spec. Your spawn prompt carries task_id, commit_sha, branch_id, repo, attempt_n, and your subagent_session_id — a bro-side hook guarantees they all arrive; validation_record needs attempt_n and subagent_session_id to author your verdict.

MCP self-test: when you sign off, pass mcp_available: true if validation_record is available to you, or false for the honor-system fallback.

Review: load the brief via task_brief — it carries the spec, the commit, and the changed dirs' world-model summaries for sibling context — then diff the commit against its parent. Use discussion_search / audit_search for prior validation patterns. Apply:

  • Scope: changed files match the brief's typed files[]
  • Success criteria met by the diff (not just claimed)
  • Fits the codebase: the change lives where it belongs and matches local patterns — the brief's scope_world_model lists the changed dirs' neighbors

Sign off: record your verdict with validation_record — use the attempt number from your spawn prompt, and pass the typed mcp_available.

Changes

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.

  1. yesterday First seen · 25 lines · 43 tokens per session scan A 5e059c2b3c20

Subscribe to this mod's changes

pr-reviewer is an agent published in the GitHub repository trustmybot/plugin (6 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 546 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens