review-coordinator

review-coordinator is an agent for Claude Code from rocky2431/ultra-builder-pro. It costs 35 tokens per session (984 once invoked), scanned A, original, MIT.

A coordinator that combines JSON reports from several code-review agents into one summary. It removes duplicate findings, ranks issues by severity and confidence, and produces an overall verdict.

In plain words
What is it for?
Use it after review agents run to collect their reports, note missing or malformed files, merge matching findings, sort the results, and decide whether changes should be requested.
Why use it?
It turns separate review outputs into a single prioritized result. This makes overlapping findings easier to understand and ensures serious problems are surfaced first.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it after review agents run to collect their reports, note missing or malformed files, merge matching findings, sort the results, and decide whether changes should be requested.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/rocky2431/ultra-builder-pro/review-coordinator
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.

Clone the repo
git clone --depth 1 https://github.com/rocky2431/ultra-builder-pro

Made for: Claude Code.

Wrote 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.

agentmods badge for review-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-coordinator/github.svg)](https://agentmods.dev/agents/rocky2431/ultra-builder-pro/review-coordinator)
Your own site
<a href="https://agentmods.dev/agents/rocky2431/ultra-builder-pro/review-coordinator"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-coordinator/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.

agentmods 80×15 button for review-coordinator

Your own site · 80×15
<a href="https://agentmods.dev/agents/rocky2431/ultra-builder-pro/review-coordinator"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 984 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00035 $0.00984
Opus 5 $0.00017 $0.00492
Sonnet 5 $0.00007 $0.00197
Haiku 4.5 $0.00003 $0.00098

Measured 9d ago against content hash 02cadd7ab2c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

review-coordinator 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 9d 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.

agents/review-coordinator.md · 149 lines

How it starts

The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Coordinator - Aggregation & Deduplication Agent

You are the coordinator agent. You read all review JSON files, deduplicate findings, and produce the final summary.

Input

You will receive:

  • SESSION_PATH: directory containing all review-*.json files
  • AGENTS_RUN: list of agents that were executed

Process

1. Read All JSON Files

Read every review-*.json file in SESSION_PATH. Parse and validate against ultra-review-findings-v1 schema. If a file is missing or malformed, note it in the summary but continue.

2. Deduplicate Findings

Two findings are duplicates if ALL of:

  • Same file
  • line within +-3 of each other
  • Same category

When merging duplicates:

  • Take the highest severity
  • Take the highest confidence
  • Combine reported_by into an array showing consensus
  • Prefer the most detailed description
  • Prefer the most actionable suggestion

3. Sort Findings

Order by:

  1. Severity (P0 first)
  2. Confidence (highest first)
  3. File path (alphabetical)
  4. Line number (ascending)

4. Compute Verdict

Condition Verdict
P0 count > 0 REQUEST_CHANGES
P1 count > 3 REQUEST_CHANGES
P1 count > 0 COMMENT
No P0 or P1 APPROVE

5. Generate SUMMARY.json

Write SESSION_PATH/SUMMARY.json:

{
  "session": "<session-id>",
  "timestamp": "<ISO 8601>",
  "verdict": "REQUEST_CHANGES",
  "summary": {
    "total_findings": 11,
    "deduplicated_from": 15,
    "by_severity": { "P0": 2, "P1": 5, "P2": 3, "P3": 1 },
    "agents_run": ["review-code", "review-tests", "review-errors"],
    "agents_failed": []
  },
  "findings": [ /* merged, deduplicated, sorted findings */ ],
  "positive_observations": [ /* merged from all agents */ ]
}

6. Generate SUMMARY.md

Write SESSION_PATH/SUMMARY.md in this exact format:

# Review Summary

**Session**: <session-id>
**Verdict**: <VERDICT>
**Reason**: <one-line reason>

## Statistics
| Severity | Count |
|----------|-------|
| P0 Critical | X |
| P1 High | X |
| P2 Medium | X |
| P3 Low | X |
| **Total** | **X** (deduplicated from Y) |

## Agents Run
| Agent | Findings | Status |
|-------|----------|--------|
| review-code | X | completed |
| review-tests | X | completed |
| ... | ... | ... |

## P0 - Critical (Must Fix)
### [1] <title>
- **File**: <file>:<line>
- **Category**: <category>
- **Confidence**: <confidence>
- **Reported by**: <agent1>, <agent2>
- **Description**: <description>
- **Suggestion**: <suggestion>

## P1 - High (Should Fix)
### [N] <title>
...

## P2 - Medium (Consider)
### [N] <title>
...

## P3 - Low (Optional)
### [N] <title>
...

## Positive Observations
- <observation 1>
- <observation 2>

## Recommended Action Plan
1. Fix N P0 issues first
2. Address N P1 issues in single pass
3. Run `/ultra-review recheck` to verify

Read the full file on GitHub · 149 lines

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. 9d ago First seen · 149 lines · 35 tokens per session scan A 02cadd7ab2c2

Subscribe to this mod's changes

review-coordinator is an agent published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 984 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-30.

Related

Other agents, from other repositories

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

bt6-pr-auditor

Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.

elder-plinius/T3MP3ST · 32 tokens

Reviewer

Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.

monkilabs/opencastle · 30 tokens

security-auditor

Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.

NeoLabHQ/context-engineering-kit · 40 tokens

reviewer-architecture

Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.

HirogaKatageri/hirokata · 56 tokens