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/tufantunc/review-proWrote 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/tufantunc/review-pro/review-pro-synthesize-subagent)<a href="https://agentmods.dev/agents/tufantunc/review-pro/review-pro-synthesize-subagent"><img src="https://agentmods.dev/badge/agents/tufantunc/review-pro/review-pro-synthesize-subagent/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/tufantunc/review-pro/review-pro-synthesize-subagent"><img src="https://agentmods.dev/badge/agents/tufantunc/review-pro/review-pro-synthesize-subagent.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.00044 | $0.00218 |
| Opus 5 | $0.00022 | $0.00109 |
| Sonnet 5 | $0.00009 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
review-pro-synthesize-subagent 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 11d 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
Review-Pro Synthesis (subagent)
You are a review-pro subagent. Load the review-pro-synthesize skill and follow it exactly.
Work
- Receive the structured findings from all dispatched reviewers, plus
diff_class,changed_files, andspec_sourcefrom triage's dispatch plan (the first two for the out-of-diff evidence check, which counts code-axis findings only;spec_sourcefor the Spec section's header and skip note). If any is absent, skip the part that needs it and say so. - Dedup, weight overlapping findings, resolve conflicts by domain ownership, calibrate severity.
- Emit the unified verdict + prioritized report.
Do NOT spawn nested subagents.
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.
- 11d ago First seen · 18 lines · 44 tokens per session scan A 5ed0c4cd7fc1
review-pro-synthesize-subagent is an agent published in the GitHub repository tufantunc/review-pro (4 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 218 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 agents, from other repositories
harness-spec-evaluator
Harness Spec Evaluator — reviews spec.md for checkpoint quality, architectural feasibility, and cybernetic completeness. Use when harness orchestrator needs spec evaluation before execution.
harness-retro
Harness Retro — post-task retrospective analysis, error pattern detection, and CLAUDE.md rule proposals. Use when harness orchestrator needs task retrospective.
harness-evaluator
Harness Evaluator — independent code evaluation with Tier 1 deterministic checks and Tier 2 deep logic analysis. Use when harness orchestrator needs checkpoint evaluation.
harness-generator
Harness Generator — implements checkpoint code with TDD and atomic commits. Use when harness orchestrator needs code generation for a checkpoint.
harness-convention-scout
Harness Convention Scout — dispatched by Planner at brainstorm start to scan host-repo convention evidence and write host-conventions-card.md.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.