review

review is a command for coding agents from valpere/chorus. It costs 12 tokens per session (546 once invoked), scanned A, original, MIT.

A command that reviews the current Git changes with several coding agents and combines their findings.

In plain words
What is it for?
Use it to check a Git diff for security, correctness, robustness, codebase consistency, maintainability, and scope.
Why use it?
Different reviewers focus on different risks, so one review is less likely to overlook a bug, edge case, or integration problem.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the chorus plugin — 5 commands shipped together

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.

agentmods
npx agentmods add commands/valpere/chorus/review
Clone the repo
git clone --depth 1 https://github.com/valpere/chorus

Or install chorus, the plugin that ships this one along with the rest of its 5 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/valpere/chorus/review.svg)](https://agentmods.dev/commands/valpere/chorus/review)
Your own site
<a href="https://agentmods.dev/commands/valpere/chorus/review"><img src="https://agentmods.dev/badge/commands/valpere/chorus/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00546
Opus 5 $0.00006 $0.00273
Sonnet 5 $0.00002 $0.00109
Haiku 4.5 $0.00001 $0.00055

Measured 5d ago against content hash ecaa84b2124e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

review 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 5d 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/chorus/commands/review.md · 66 lines

What it actually says

Run a parallel code review across five agents and synthesize the findings.

Raw slash-command arguments: $ARGUMENTS

Review focus per agent:

  • Claude — correctness and security (bugs, vulnerabilities, unsafe patterns)
  • Gemini — edge cases and robustness (missing error handling, race conditions)
  • Codex — scope and simplicity (unnecessary complexity, simpler alternatives)
  • Cursor — codebase integration (consistency with existing patterns, dependency risks)
  • Kilo — maintainability (readability, naming clarity, long-term tech debt)

Each agent reviews the current git diff HEAD.

Execution mode:

  • Default: background (reviews are slow).
  • If --wait is in the arguments, run in foreground.
  • If --json is in the arguments, the companion emits {"command":"review","results":[{name,output,error,exitCode}]} on stdout instead of delimited text. Warnings still go to stderr.
  • Strip --background, --wait, and --json before passing to companion.

Pre-flight: The companion automatically checks which agents are installed. Missing agents are reported in stdout with install instructions. The review proceeds with whatever agents are available — at least 2 are required; if fewer are installed the companion exits non-zero and you should tell the user to install more agents.

Foreground execution:

node "$CLAUDE_PLUGIN_ROOT/scripts/companion.mjs" review $ARGUMENTS

Background execution:

Bash({
  command: `node "$CLAUDE_PLUGIN_ROOT/scripts/companion.mjs" review $ARGUMENTS`,
  description: "Parallel code review",
  run_in_background: true
})

Tell the user: "Parallel review started in the background. You'll be notified when it completes."

After the companion exits, synthesize:

## Parallel Review Summary

**Critical findings** (flagged by 2+ agents):
- …

**Individual findings** (columns = available agents):
| Finding | Agent 1 | Agent 2 | … |
|---------|---------|---------|---|
| …       | ✓       |         |   |

## Verdict

<1–2 sentences: overall code health and whether changes should proceed as-is or need revision.>

This is a review-only command — do not fix issues or apply patches.

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. 5d ago First seen · 66 lines · 12 tokens per session scan A ecaa84b2124e

Subscribe to this mod's changes

review is a command published in the GitHub repository valpere/chorus (10 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 546 once invoked, about $0.0001 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.

Related

Other commands, from other repositories

update-ai-versions

Look up the latest published versions of the AI coding assistants pinned in the Dockerfile and update the ARG lines in place.

sugarfreebytes/aidevtools · 24 tokens

yapper-help

The /yapper-help command displays full documentation for the Yapper plugin, including all modes, commands, behaviours, configuration options, and usage examples. This command is itself rendered in Professor mode by default, because a help document that is not thoroughly elaborated would be somewhat contrary to the…

dzan314/yapper · 0 tokens

yapper-review

The /yapper-review command performs a thorough, multi-line pull request review. Rather than posting terse inline comments like "this is wrong" or "use X instead," yapper-review produces fully-explained feedback that describes the issue, the reasoning behind the concern, the potential impact, and a concrete suggested…

dzan314/yapper · 0 tokens

yapper-commit

The /yapper-commit command generates a verbose, fully-explained Git commit message for the current change or a described change. The resulting commit message explains not just what changed, but why it changed, what problem it solves, and how the solution works — providing maximum context for future readers of the git…

dzan314/yapper · 0 tokens

yapper

The /yapper command activates the Yapper verbosity system. Once active, all subsequent responses in the session will be substantially expanded, elaborated, and enriched with definitions, transitions, and restatements.

dzan314/yapper · 0 tokens

mem-last

Prints latest memory cards for the current project.

djinn-soul/gemini-mem · 0 tokens