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.
npx agentmods add commands/vit129/agy-plugin-cc/adversarial-reviewgit clone --depth 1 https://github.com/Vit129/agy-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/vit129/agy-plugin-cc/adversarial-review)<a href="https://agentmods.dev/commands/vit129/agy-plugin-cc/adversarial-review"><img src="https://agentmods.dev/badge/commands/vit129/agy-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 | $0.00015 | $0.00721 |
| Opus 5 | $0.00008 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00002 | $0.00072 |
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 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.
This is a copy
83% identical to adversarial-review — 37 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.
What it actually says
Run an adversarial agy review. Position it as a challenge review that questions the chosen implementation, design choices, tradeoffs, and assumptions — not just a stricter pass over defects.
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.
- Keep the framing focused on whether the current approach is the right one, what assumptions it depends on, and where the design could fail under real-world conditions.
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 in the foreground. - If the raw arguments include
--background, do not ask. Run in a Claude background task. - Otherwise, estimate the review size before asking:
- For working-tree review, run
git status --short --untracked-files=all. - Also inspect
git diff --shortstat --cachedandgit diff --shortstat. - For base-branch review, use
git diff --shortstat <base>...HEAD. - Treat untracked files as reviewable work even when
git diff --shortstatis empty. - Only conclude there is nothing to review when the relevant scope is actually empty.
- Recommend waiting only when the review is clearly tiny (roughly 1–2 files).
- In every other case, recommend background.
- For working-tree review, run
- Then use
AskUserQuestionexactly once with two options, putting the recommended option first and suffixing its label with(Recommended):Wait for resultsRun in background
Argument handling:
- Preserve the user's arguments exactly.
- Do not strip
--waitor--backgroundyourself. - Do not weaken the adversarial framing or rewrite the user's focus text.
Foreground flow:
- Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" adversarial-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
Bashin the background:
Bash({
command: `node "${CLAUDE_PLUGIN_ROOT}/scripts/agy-companion.mjs" adversarial-review "$ARGUMENTS"`,
description: "agy adversarial review",
run_in_background: true
})
- Do not wait for completion in this turn.
- After launching the command, tell the user: "agy adversarial review started in the background. Check
/agy:statusfor progress."
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.
- 5d ago First seen · 60 lines · 15 tokens per session scan A 89bac84b8689
adversarial-review is a command published in the GitHub repository Vit129/agy-plugin-cc (5 stars, last pushed 12d ago), licensed MIT. It adds 15 tokens to every session and 721 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 37 lines, and is treated as a copy.
Other commands, from other repositories
delegate
Hand a task to Antigravity (Gemini 3.5) and get the result back inside Claude Code.
review
Cross-model code review of your changes by Gemini 3.5 (read-only, contained).
resume
Continue the most recent Antigravity (Gemini 3.5) conversation with a follow-up.
result
Show the final output (and conversation id) of a finished Antigravity job.
cancel
Cancel a running background Antigravity job.
status
Show running and recent Antigravity jobs for this repo.