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/adversarial-review)<a href="https://agentmods.dev/commands/haunchen/gemini-plugin-cc/adversarial-review"><img src="https://agentmods.dev/badge/commands/haunchen/gemini-plugin-cc/adversarial-review.svg" alt="Measured on agentmods" 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.00011 | $0.00772 |
| Opus 5 | $0.00005 | $0.00386 |
| Sonnet 5 | $0.00002 | $0.00154 |
| Haiku 4.5 | $0.00001 | $0.00077 |
Grade A, and why
adversarial-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 6d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Get a devil's advocate review using Gemini via the Antigravity CLI (agy). Instead of finding bugs, this challenges your design decisions and proposes alternatives.
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 2: Determine input
If $ARGUMENTS (after --model 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
Step 3: Call agy
The system prompt lives in the gemini-adversarial-review agent, installed by /gemini:setup. The agent's tools whitelist keeps the run read-only — there is no separate policy file.
Run the following bash command, passing REVIEW_INPUT via stdin:
output=$(printf "%s" "$REVIEW_INPUT" | agy --agent gemini-adversarial-review --model $MODEL --print-timeout 5m 2>&1)
echo "$output"
Note: We pipe input via stdin instead of -p to handle large diffs and special characters safely.
If the output says no output produced and names a denied permission (read_file), the agent tried to open a file and agy auto-denied it: a headless run cannot show a permission prompt, and the denial throws away the whole review. The install is fine — re-run, and note that whether the agent reaches for a file depends on what it finds in the diff, so this does not reproduce every time.
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.
- 6d ago First seen · 60 lines · 0 tokens per session scan A 6709399ccb04
adversarial-review is a command published in the GitHub repository haunchen/gemini-plugin-cc (1 stars, last pushed 23d ago), licensed MIT. It adds 11 tokens to every session and 772 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-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.