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.
git clone --depth 1 https://github.com/haunchen/gemini-plugin-ccWrote 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.
[](https://agentmods.dev/commands/haunchen/gemini-plugin-cc/review)<a href="https://agentmods.dev/commands/haunchen/gemini-plugin-cc/review"><img src="https://agentmods.dev/badge/commands/haunchen/gemini-plugin-cc/review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/haunchen/gemini-plugin-cc/review"><img src="https://agentmods.dev/badge/commands/haunchen/gemini-plugin-cc/review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.01824 |
| Opus 5.5 | $0.00000 | $0.00730 |
| Sonnet 5.5 | $0.00000 | $0.00365 |
| Haiku 4.5 | $0.00000 | $0.00182 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Perform a code review using Gemini via the Antigravity CLI (agy). This gives you a second opinion from a different AI model.
Step 1: Parse --model parameter
Check if $ARGUMENTS contains --model <value>:
- If yes: extract the value as MODEL, remove
--model <value>from $ARGUMENTS - If no: set MODEL = flash
Map the alias to an agy model slug:
flash→gemini-3.6-flash-high(the default)pro→gemini-3.1-pro-high— an older generation than 3.6 flash; available for explicit opt-in, not recommended- Anything else is passed through unchanged (run
agy modelsto list available slugs).
Step 1b: Parse --spec parameter
Check if $ARGUMENTS contains one or more --spec <path> pairs:
- If none: set SPEC_INPUT = empty, skip the rest of this step
- For each
--spec <path>found:- If the path contains glob characters (* or ?), use the Glob tool to expand it, then Read each matched file
- Otherwise, Read the single file directly
- If a path does not exist, tell the user which one and stop — a silently missing requirements file would produce a spec-compliance verdict based on nothing
- If
--specis not followed by a value, or is followed by something starting with--, tell the user it needs a path and stop — do not consume the next flag as a filename
- Remove every
--spec <value>pair from $ARGUMENTS - Concatenate all spec file contents (separated by a blank line) as SPEC_INPUT
--spec and --model may appear in any order, before or after the file path.
Step 2: Determine input
If $ARGUMENTS (after --model and --spec removal) is provided:
- If it contains glob characters (* or ?), use the Glob tool to expand it, then Read each matched file
- Otherwise, Read the single file directly
- Concatenate all file contents as REVIEW_INPUT
If $ARGUMENTS is empty:
- Run:
git diff HEAD 2>/dev/null - If the command fails (e.g., no commits yet) or the diff is empty, also try:
git diff --cached - If still empty, tell the user: "No changes found. Provide a file path or make some changes first."
- Store the diff output as REVIEW_INPUT
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.
- 1mo ago First seen · 115 lines · 0 tokens per session scan A bea958a65f56
review is a command published in the GitHub repository haunchen/gemini-plugin-cc (1 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,824 tokens. 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.
Other commands, from other repositories
review
Get an independent cross-model review of the current diff from Antigravity (Gemini), then reconcile as the final judge.
review
Send the current git diff to Antigravity (agy) for code review. Optional focus text to steer the review.
gemini-validate
Get a Gemini second opinion on a plan, diff, or claim.
agy-review
Send the current change set to Antigravity (agy) for a senior-reviewer code review.
review
Run a Gemini code review against local git state.
adversarial-review
Run a Gemini review that challenges the implementation approach and design choices.