agentmods.dev

review

review is a command for coding agents from zachdunn/grok-plugin-claude-code. It costs 12 tokens per session (517 once invoked), scanned A, original, MIT.

A command that runs a read-only Grok review of the current Git changes. Git is the version-control system used to track code changes.

In plain words
What is it for?
Reviewing uncommitted work or comparing a branch with another Git reference, including checking untracked files.
Why use it?
It helps inspect proposed changes without modifying files, while choosing whether the review should run immediately or in the background.

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 grok-cc plugin — 3 skills, 4 commands, 1 agent, 1 hook shipped together

not rated 29 2mo ago A scan 12 tokens original MIT
View the source file zachdunn/grok-plugin-claude-code
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/zachdunn/grok-plugin-claude-code/review
Clone the repo
git clone --depth 1 https://github.com/zachdunn/grok-plugin-claude-code

Or install grok-cc, the plugin that ships this one along with the rest of its 3 skills, 4 commands, 1 agent, 1 hook.

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/zachdunn/grok-plugin-claude-code/review.svg)](https://agentmods.dev/commands/zachdunn/grok-plugin-claude-code/review)
Your own site
<a href="https://agentmods.dev/commands/zachdunn/grok-plugin-claude-code/review"><img src="https://agentmods.dev/badge/commands/zachdunn/grok-plugin-claude-code/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 517 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.00517
Opus 5 $0.00006 $0.00259
Sonnet 5 $0.00002 $0.00103
Haiku 4.5 $0.00001 $0.00052

Measured 4d ago against content hash ae0b9e491e11, 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 4d 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-cc/commands/review.md · 40 lines

What it actually says

Run a Grok code review through the companion runtime.

Raw slash-command arguments: $ARGUMENTS

Core constraint:

  • This command is review-only. Do not fix issues, apply patches, or imply you are about to make changes.
  • Your only job is to run the review and return Grok's output verbatim to the user.

Execution mode:

  • If the arguments include --wait, run in the foreground without asking.
  • If the arguments include --background, run as a Claude background task without asking.
  • Otherwise, estimate the review size first:
    • For a working-tree review (no --base), run git status --short --untracked-files=all, git diff --shortstat, and git diff --shortstat --cached. Treat untracked files as reviewable work even when the diff stat is empty.
    • For a branch review (--base <ref> given), run git diff --shortstat <ref>...HEAD.
    • Only conclude there is nothing to review when the relevant status and diff are genuinely empty.
    • Recommend waiting only when the change is clearly tiny (~1-2 files). In every other case, including unclear size, recommend background.
    • Use AskUserQuestion exactly once with two options, recommended option first and suffixed (Recommended): Wait for results and Run in background.

Run the review:

node "${CLAUDE_PLUGIN_ROOT}/scripts/grok-companion.mjs" review <args>
  • Pass the user's arguments through unchanged (the companion parses --base, --scope, --adversarial, --background, and trailing focus text). Do not rewrite the user's intent.
  • For a backgrounded run, invoke the Bash call with run_in_background: true.
  • Return the companion's stdout as-is, findings first, ordered by severity. Do not add your own analysis.

If the companion reports Grok is not installed or not signed in, tell the user to run /grok-cc:setup. For deeper, skeptical review, point them at /grok-cc:adversarial-review.

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. 4d ago First seen · 40 lines · 12 tokens per session scan A ae0b9e491e11

Subscribe to this mod's changes

review is a command published in the GitHub repository zachdunn/grok-plugin-claude-code (29 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 517 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-30.

Code reviewai-agentsclaude-codegrokgrok-clipluginxai
Related

Other commands, from other repositories

critique

Run a Grok Build critique that challenges the implementation approach and design choices.

kai-wedekind/claude-code-grok-bridge · 14 tokens

check

Check whether the local Grok Build CLI is ready for the Claude Code bridge.

kai-wedekind/claude-code-grok-bridge · 15 tokens

implement

Claude plans, Grok implements - write a concrete implementation plan, hand it to Grok as the worker, wait, then verify the result.

davit-khaburdzania/grok-plugin-cc · 28 tokens

review

Run a Grok code review against local git state.

davit-khaburdzania/grok-plugin-cc · 10 tokens

consult

Ask Grok a free-form question, optionally with file context (read-only).

faeton/claude-grok-plugin · 16 tokens

review

Run a Grok code review against local git state (read-only).

faeton/claude-grok-plugin · 14 tokens