← ClaudeAtlas

agy-adversarial-reviewlisted

Run an adversarial (red-team) review through the Antigravity CLI (`agy`, Gemini family). Use when the user asks for an adversarial review from Gemini/Antigravity, wants a second model family's opinion, or when another family's quota is tight and a different reviewer is needed. Pick a reviewer whose blind spots differ from the author's.
aarontzeng/dev-lead · ★ 1 · Code & Development · score 67
Install: claude install-skill aarontzeng/dev-lead
# Adversarial review via `agy` (Antigravity CLI) `agy` is an independent path to a different model family — the reason to use it is **model diversity**, not convenience. A reviewer that shares the author's training shares the author's blind spots, so the value of this skill comes entirely from the reviewer being something other than the model that wrote the code. Pairing rule across the suite: **the reviewer must come from a different model family than whatever implemented the change.** When quota is tight, spend the scarce model on review rather than implementation — review leverage is higher. ## Before the first run of a session Read **[`references/agy-runtime.md`](references/agy-runtime.md)** (same directory). It holds the family-level mechanics shared with `agy-implement` — the permission allow-list this CLI needs before it can run `git` at all, the `--add-dir` workspace trap, the silent-death mode, the auth diagnosis, and the model catalogue. Every item in it was paid for with an incident; this file assumes you know them and covers only what makes a run a *review*. The one-line version of the three that bite hardest: the allow-list is required or every git command is auto-denied; `--add-dir` is mandatory because the headless workspace root is agy's own scratch dir; and a run that returns nothing did not necessarily do nothing. ## Establish an immutable review target **One frozen directory per reviewer, at the exact commit, that nothing else touches — no lead activ