agentmods.dev

review

review is a command for coding agents from Agents365-ai/pi-plugin-cc. It costs 9 tokens per session (573 once invoked), scanned A, original, Apache-2.0.

A command that runs a Pi code review on the repository's current Git changes. Git is a system for tracking code changes; the command only reviews and does not edit files.

In plain words
What is it for?
Use it to review a working-tree or branch diff, optionally with multiple models or incremental review. It reports Pi's review output, or says when there is nothing to review.
Why use it?
It gives a review of the current changes without mixing review results with automatic fixes. It can also review changes since a previous review or compare against a chosen base when supported by its options.

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 pi plugin — 3 skills, 8 commands, 1 agent, 3 hooks shipped together

not rated 44 +1 21d ago A scan 9 tokens original Apache-2.0
View the source file Agents365-ai/pi-plugin-cc
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/agents365-ai/pi-plugin-cc/review
Clone the repo
git clone --depth 1 https://github.com/Agents365-ai/pi-plugin-cc

Or install pi, the plugin that ships this one along with the rest of its 3 skills, 8 commands, 1 agent, 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 review

README.md
[![agentmods](https://agentmods.dev/badge/commands/agents365-ai/pi-plugin-cc/review.svg)](https://agentmods.dev/commands/agents365-ai/pi-plugin-cc/review)
Your own site
<a href="https://agentmods.dev/commands/agents365-ai/pi-plugin-cc/review"><img src="https://agentmods.dev/badge/commands/agents365-ai/pi-plugin-cc/review.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 573 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.00009 $0.00573
Opus 5 $0.00005 $0.00287
Sonnet 5 $0.00002 $0.00115
Haiku 4.5 $0.00001 $0.00057

Measured 5d ago against content hash 4f9d9cfc518b, 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/pi/commands/review.md · 36 lines

What it actually says

Run a Pi review through the shared plugin runtime.

Raw slash-command arguments: $ARGUMENTS

Core constraint:

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

Execution:

  • Run the review in the foreground.
  • If there is nothing to review (empty working tree and no base branch diff), say so and skip the review.
  • /pi:review does not accept extra focus text. If the user needs custom review instructions or more adversarial framing, they should use /pi:adversarial-review.
  • --incremental only reviews commits since the last review on the current branch (cached per branch); falls back to a full review when there is no valid cache (no prior review, or the cached commit is no longer an ancestor of HEAD, e.g. after a rebase). Not combinable with --base. Composes with --models/--shards.
  • --models <m1,m2,...> (2+ models) runs a multi-model review panel: the same diff is reviewed by every listed model in parallel and the findings are merged, with consensus findings (reported by 2+ models) ranked first.
  • --shards <N> (N >= 2, and only when more than one file changed) splits the changed files across N review jobs that run in parallel, each scoped to only its own files, then merges the findings into one result. Not combinable with --models.
  • --out-file <path> writes the full review to <path> and returns only a short summary (verdict, finding counts, one line per finding) — this keeps a large review out of the conversation's context to save tokens. When it is used, relay the short summary verbatim; the user opens the file for the full detail.

Foreground flow:

  • Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/pi-companion.mjs" review "$ARGUMENTS"
  • Return the command stdout verbatim, exactly as-is.
  • Do not paraphrase, summarize, or add commentary before or after it.
  • Do not fix any issues mentioned in the review output.
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 · 36 lines · 9 tokens per session scan A 4f9d9cfc518b

Subscribe to this mod's changes

review is a command published in the GitHub repository Agents365-ai/pi-plugin-cc (44 stars, last pushed 21d ago), licensed Apache-2.0. It adds 9 tokens to every session and 573 once invoked, about $0.0000 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 reviewGit and workflowclaude-codeclaude-code-plugincoding-agentdeepseekpi-coding-agent
Related

Other commands, from other repositories

review

Run a read-only Grok code review of your uncommitted changes or a branch.

VasiHemanth/grok-build-plugin · 17 tokens

search

Search X (Twitter) and the web in real time with Grok, then summarize with sources.

VasiHemanth/grok-build-plugin · 19 tokens

result

Show the final output of a completed Grok job.

VasiHemanth/grok-build-plugin · 10 tokens

kill

Stop a running cli-dispatch worker session.

rbinar/cli-dispatch · 8 tokens

cancel

Cancel a running background Grok job.

VasiHemanth/grok-build-plugin · 7 tokens

ag-run

Delegate a task to the Antigravity (agy / Gemini) worker.

rbinar/cli-dispatch · 14 tokens