agentmods.dev

aggregate-review

aggregate-review is a command for Claude Code from LovelaceLoom/grok-plugin-cc. It costs 35 tokens per session (598 once invoked), scanned A, original, Apache-2.0.

A command that starts a combined code review by sending the same request to Codex, Gemini, and Grok in parallel.

In plain words
What is it for?
Use it to review working-tree, staged, or branch changes, with foreground or background execution depending on the request.
Why use it?
It collects independent review results and produces one unified report, saving you from running and comparing three reviews manually.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool; 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 grok plugin — 8 skills, 21 commands, 2 agents, 3 hooks shipped together

not rated 5repo 1mo ago A scan 35 tokens original Apache-2.0

Good fit Use it to review working-tree, staged, or branch changes, with foreground or background execution depending on the request.

Compare 6 commands from other repositories ↓
View source ↗ LovelaceLoom/grok-plugin-cc
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 LovelaceLoom/grok-plugin-cc
Claude Code
/plugin install grok

Made for: Claude Code.

Or install grok, the plugin that ships this one along with the rest of its 8 skills, 21 commands, 2 agents, 3 hooks.

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 aggregate-review

README.md
[![agentmods](https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/aggregate-review.svg)](https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/aggregate-review)
Your own site
<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/aggregate-review"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/aggregate-review.svg" alt="Measured on agentmods" 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 598 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.00598
Opus 5 $0.00017 $0.00299
Sonnet 5 $0.00007 $0.00120
Haiku 4.5 $0.00003 $0.00060

Measured 8d ago against content hash 210ccddddfe9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

aggregate-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 8d 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/grok/commands/aggregate-review.md · 50 lines

What it actually says

Invoke the grok:grok-aggregate-review subagent via the Agent tool (subagent_type: "grok:grok-aggregate-review"), forwarding the raw user request as the prompt. The final user-visible response must be the companion's output verbatim.

Raw user request: $ARGUMENTS

Execution mode:

  • If the request includes --background, run the subagent in the background.
  • If the request includes --wait, run the subagent in the foreground.
  • If neither flag is present, default to foreground for typical reviews and background for diffs larger than ~50 KB or when the user signals patience.
  • --background and --wait are Claude-Code execution controls. Do not forward them to the companion's aggregate-review subcommand.

Operating rules:

  • The subagent is a thin forwarder only. It uses one Bash call to invoke node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" aggregate-review ... and returns that command's stdout as-is.
  • Return the companion's stdout verbatim to the user.
  • Do not paraphrase, summarize, rewrite, or add commentary before or after it.
  • If $ARGUMENTS is empty, ask the user whether to review the working tree, staged changes, or a branch diff before invoking the subagent.
  • If the companion reports that fewer than 2 peer CLIs are installed, surface that and stop. The user needs at least Codex + Gemini, Codex + Grok, or Gemini + Grok installed for the aggregator to be useful.

This is the meta-aggregator — useful when you want multi-LLM consensus on whether a change is ready to merge. Each reviewer brings a distinct style:

  • Codex — strongest at deep correctness analysis and concrete file:line bugs.
  • Gemini — strongest at large-context cross-file reasoning and security-property tracing.
  • Grok — strongest at fresh-context skepticism and unconventional angles.

Requires at least two of the three CLIs installed. The per-reviewer timeout defaults to 10 minutes.

Pass --adversarial to switch each reviewer's prompt to the more aggressive adversarial-review template (challenges the design, surfaces failure modes).

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. 8d ago First seen · 50 lines · 35 tokens per session scan A 210ccddddfe9

Subscribe to this mod's changes

aggregate-review is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 598 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.

Claude CodeCode reviewai-assistantai-toolsclaude-code-plugindeveloper-tools
Related

Other commands, from other repositories

review

Multi-agent code review with parallel validation.

Joncik91/ucai · 7 tokens

gemini-validate

Get a Gemini second opinion on a plan, diff, or claim.

azmym/gemini-plugin · 13 tokens

open-pr

Create a pull request for the current branch following the the team's standard PR template.

carloshpdoc/ios-workflow-claude · 0 tokens

apollo-review

Review the completed migration for $ARGUMENTS against the original investigation and produce a detailed report.

carloshpdoc/ios-workflow-claude · 0 tokens

code-review

Review code quality applying DRY, SOLID, naming, and formatting standards.

carloshpdoc/ios-workflow-claude · 18 tokens

review-pr

Review the pull request $ARGUMENTS and post inline comments using the authenticated GitHub user.

carloshpdoc/ios-workflow-claude · 0 tokens