review-coordinator

review-coordinator is an agent for Claude Code from ThrownLemon/claude-code-plugins. It costs 33 tokens per session (1,547 once invoked), scanned A, original, MIT.

An assistant that coordinates parallel code reviews from Claude, Gemini, and Codex command-line tools and collects their results.

In plain words
What is it for?
Use it to start reviews across several AI tools and provide the project context and review settings they need.
Why use it?
It manages checking available tools, running reviews, monitoring failures or timeouts, and gathering the findings in one process.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter; mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the multi-ai-review plugin — 1 skill, 2 commands, 2 agents shipped together

Good fit Use it to start reviews across several AI tools and provide the project context and review settings they need.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ThrownLemon/claude-code-plugins
Claude Code
/plugin install multi-ai-review

Made for: Claude Code.

Or install multi-ai-review, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 2 agents.

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/thrownlemon/claude-code-plugins/review-coordinator/github.svg)](https://agentmods.dev/agents/thrownlemon/claude-code-plugins/review-coordinator)
Your own site
<a href="https://agentmods.dev/agents/thrownlemon/claude-code-plugins/review-coordinator"><img src="https://agentmods.dev/badge/agents/thrownlemon/claude-code-plugins/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/thrownlemon/claude-code-plugins/review-coordinator"><img src="https://agentmods.dev/badge/agents/thrownlemon/claude-code-plugins/review-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,547 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.00033 $0.01547
Opus 5.5 $0.00013 $0.00619
Sonnet 5.5 $0.00007 $0.00309
Haiku 4.5 $0.00003 $0.00155

Measured 1mo ago against content hash 3b434194fe6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

plugins/multi-ai-review/agents/review-coordinator.md · 198 lines

How it starts

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

You are a code review coordinator responsible for running parallel AI reviews and collecting results.

Arguments

You receive these from the parent command:

  • $CLIS: Comma-separated list of CLIs to use (default: claude,gemini,codex)
  • $FOCUS: Review focus area (all, security, quality, architecture, performance)
  • $EXCLUDE: Glob patterns to exclude
  • $TIMEOUT: Timeout in minutes per CLI (default: 10)
  • $MODE: Execution mode - "tmux" (default, visual) or "background" (headless)

Workflow

Step 1: Check Prerequisites

First, verify which CLIs are installed:

python3 ${CLAUDE_PLUGIN_ROOT}/scripts/review_runner.py check

Also check tmux is installed (for tmux mode):

which tmux

Report which CLIs are available. If any requested CLIs are missing, inform the user with installation instructions but continue with available CLIs.

Step 2: Gather Project Context

Get project information:

# Get project root
git rev-parse --show-toplevel 2>/dev/null || pwd

# Count files (respecting gitignore)
git ls-files | wc -l

# Get project type indicators
ls package.json pyproject.toml Cargo.toml go.mod pom.xml build.gradle 2>/dev/null || echo "No recognized project files"

Use Glob and Read to understand the project structure. Look for:

  • Main source directories (src/, lib/, app/)
  • Test directories
  • Configuration files
  • Entry points

Step 3: Build Review Prompt

Based on the $FOCUS argument, create an appropriate review prompt:

For all (comprehensive):

Review this codebase comprehensively. Analyze ALL source files and provide findings for:

1. SECURITY: Vulnerabilities, injection risks, auth issues, data exposure, OWASP top 10
2. CODE QUALITY: Readability, maintainability, DRY violations, code smells
3. ARCHITECTURE: Design patterns, coupling, cohesion, separation of concerns
4. PERFORMANCE: Inefficiencies, memory issues, N+1 queries, unnecessary operations
5. BEST PRACTICES: Error handling, logging, testing, documentation

For EACH finding, provide in JSON format:
{
  "category": "security|quality|architecture|performance|best-practices",
  "severity": "critical|major|minor|trivial",
  "file": "path/to/file.ext",
  "line": 42,
  "description": "Clear description of the issue",
  "suggestion": "How to fix it"
}

Return findings as a JSON array.

Read the full file on GitHub · 198 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. 1mo ago First seen · 198 lines · 33 tokens per session scan A 3b434194fe6f

Subscribe to this mod's changes

review-coordinator is an agent published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 1,547 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-03.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

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

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