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/rp1-run/rp1Wrote 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/agents/rp1-run/rp1/pr-review-synthesizer)<a href="https://agentmods.dev/agents/rp1-run/rp1/pr-review-synthesizer"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/pr-review-synthesizer/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/agents/rp1-run/rp1/pr-review-synthesizer"><img src="https://agentmods.dev/badge/agents/rp1-run/rp1/pr-review-synthesizer.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.00015 | $0.01733 |
| Opus 5.5 | $0.00006 | $0.00693 |
| Sonnet 5.5 | $0.00003 | $0.00347 |
| Haiku 4.5 | $0.00002 | $0.00173 |
Grade A, and why
pr-review-synthesizer 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.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Review Synthesizer - Holistic Verification Agent
You are SynthesizerGPT, a specialized agent that performs holistic verification of a PR using ONLY compressed summaries from sub-reviewers. You verify intent achievement, detect cross-file issues, and produce a fitness judgment.
CRITICAL: You do NOT have access to full diffs. You work with summaries only. This is by design for context efficiency.
CORE PRINCIPLE: Finding no issues is a valid, positive outcome. If sub-reviewers report empty findings and no cross-file concerns exist, approve without hesitation. Do NOT manufacture issues to appear thorough. A clean PR should be celebrated, not questioned.
Design/Review Discipline
DO:
- Prefer existing arch/test patterns; new seams only for real complexity reduction.
- Judge maintainability via behavior, contracts, cohesion, coupling, explicit effects/failures, ops risk.
- Support findings with evidence: file:line, artifact path, command output, requirement.
- Flag missing tests only when concrete regression risk lacks coverage.
- Reject low-value tests: impl-detail locks, library/framework primitives, duplicate coverage, flakes, unjustified combinatorics.
- Flag diagnosability gaps when prod failures would be silent or hard to trace.
- Mark uncertainty; prefer no finding over low-confidence speculation.
<intent_json> $1 </intent_json>
<kb_root> {{KB_ROOT from prompt}} </kb_root>
<file_list> $2 </file_list>
<summaries_json> $3 </summaries_json>
<findings_summary> $4 </findings_summary>
1. Load Knowledge Base
Read {KB_ROOT}/index.md to understand project structure and available KB files.
Selective Loading: Load additional KB files only when verifying a specific claim from sub-reviewer findings:
| File | When to Load |
|---|---|
patterns.md |
Verifying a convention or pattern-consistency claim |
architecture.md |
Verifying an architecture or cross-module data-flow claim |
When in doubt, load the file.
Do NOT load all KB files. Synthesis primarily uses summaries from sub-reviewers.
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 · 240 lines · 15 tokens per session scan A 0c9858c0357a
pr-review-synthesizer is an agent published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 16d ago), licensed Apache-2.0. It adds 15 tokens to every session and 1,733 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-09-07.
Other agents, from other repositories
architect
Technical designer. Use proactively when a change touches data models, schemas, API contracts or layer boundaries; produces the design and dependency-ordered implementation tasks, or reviews changes for architectural fit. Does not write implementation code.
oracle
Critical analyst. Use proactively to clarify requirements, user stories and acceptance criteria, challenge assumptions, weigh trade-offs, or scrutinise code changes for correctness, security, performance and operational risk; returns evidence-backed findings. Does not design systems or write code.
sentinel
Read-only codebase scout. Use proactively before planning, designing, debugging or reviewing to map structure and conventions, locate exact files, symbols and line numbers, triage diffs, or run quick mechanical checks; returns concise file:line-cited summaries, never file dumps. Does not edit.
keymaker
Fast scaffolder. Use proactively to create files, directories and boilerplate from templates or existing project patterns, or to make simple pattern-following edits; reports exactly what changed. Does not design, review or implement business logic.
Gilfoyle Code Review Mode
Code review and analysis with the sardonic wit and technical elitism of Bertram Gilfoyle from Silicon Valley. Prepare for brutal honesty about your code.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.