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.00391 |
| Opus 5.5 | $0.00018 | $0.00156 |
| Sonnet 5.5 | $0.00009 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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 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
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, each code reviewer's
## Files examinedblock and each owner's## Repository rulesblock and## Premise verificationblock from all dispatched reviewers, plusdiff_class,changed_files,spec_source,external_premises,premises_dropped,repository_rules,rules_dropped,stack_signals, and each dispatched reviewer'scontext.changed_filesfrom triage's dispatch plan (external_premises,premises_droppedand the## Premise verificationblocks for External premises;repository_rulesandrules_droppedfor Repository rules;stack_signalsfor Stack signals;diff_classandchanged_filesfor the out-of-diff evidence check, which counts code-axis findings only;changed_files,diff_classand the per-reviewer lists for Coverage;spec_sourcefor the Spec section's header and skip note), and the verification results when the orchestrator ran the verifiers. If any is absent, skip the part that needs it and say so. With no verification results, apply the no-verifier rule in the skill's## Verification. - 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.
- 1mo ago Changed bb00e32203e3
- 1mo ago Changed 3797f335a880
- 1mo ago Changed 823f35ae553b
- 1mo 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 (5 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 391 once invoked, about $0.0002 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-31.
Other agents, from other repositories
iteration-guard
The verify gate of the Logic-Lens iteration loop. Given a baseline iteration and a candidate iteration, compares their summary.json (overall, logic vs format subscores, per-mode, per-language), accounts for single-run variance, and returns a SHIP / ROLLBACK / RERUN recommendation with evidence. Use after…
skill-editor
Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…
eval-failure-analyzer
Analyze Logic-Lens benchmark/eval failures. Use after running content-evals, or when pointed at a skills-workspace/iteration- directory or a benchmarks/runs/ entry, to cluster failing cases by failure mode, map each mode to the specific eval IDs, and propose concrete SKILL.md disambiguation-rule changes. Read-only…
code-reviewer
Expert in code review, security analysis, and software quality assessment.
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.