A command that asks agy to review the current Git changes or a comparison with a base branch. It reports findings without changing files.

Use it to inspect work before committing or merging, review changes against another branch, or run a dry run to see available options.

It gives you a code review without mixing review results with automatic fixes. It also accounts for staged, unstaged, and untracked work.

review — Command by Vit129

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/vit129/agy-plugin-cc/review

Clone the repo

git clone --depth 1 https://github.com/Vit129/agy-plugin-cc

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 654 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 83% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00010	$0.00654
Opus 5	$0.00005	$0.00327
Sonnet 5	$0.00002	$0.00131
Haiku 4.5	$0.00001	$0.00065

Measured 2d ago against content hash 2091f2b6e27b, 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 2d 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.

Origin

This is a copy

83% identical to adversarial-review — 43 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/agy/commands/review.md · 58 lines

What it actually says

Run an agy review by delegating to agy with a structured review prompt.

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 agy's output verbatim to the user.

Execution mode rules:

If the raw arguments include --dry-run, do not ask. Run in the foreground — it only prints the resolved options and available models, no review is performed.
If the raw arguments include --wait, do not ask. Run the review in the foreground.
If the raw arguments include --background, do not ask. Run the review in a Claude background task.
Otherwise, estimate the review size before asking:
- For working-tree review, run git status --short --untracked-files=all.
- For working-tree review, also inspect git diff --shortstat --cached and git diff --shortstat.
- For base-branch review, use git diff --shortstat <base>...HEAD.
- Treat untracked files as reviewable work even when git diff --shortstat is empty.
- Only conclude there is nothing to review when the relevant scope is actually empty.
- Recommend waiting only when the scoped review is clearly tiny (roughly 1–2 files, no sign of a broader change).
- In every other case, recommend background.
Then use AskUserQuestion exactly once with two options, putting the recommended option first and suffixing its label with (Recommended):
- Wait for results
- Run in background

Argument handling:

Preserve the user's arguments exactly.
Do not strip --wait or --background yourself.

Foreground flow:

Run:

node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-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.

Background flow:

Launch the review with Bash in the background:

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

Do not wait for completion in this turn.
After launching the command, tell the user: "agy review started in the background. Check /agy:status for progress."

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.

2d ago First seen · 58 lines · 10 tokens per session scan A 2091f2b6e27b

Subscribe to this mod's changes

review is a command published in the GitHub repository Vit129/agy-plugin-cc (5 stars, last pushed 10d ago), licensed MIT. It adds 10 tokens to every session and 654 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to adversarial-review, differing in 43 lines, and is treated as a copy.

Code review Git and workflow agy antigravity antigravity-ide claude-code claude-code-plugin google-antigravity

review

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

adversarial-review

review

result

status

cancel

image