Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nikuscs/codex-cc-pluginnpx agentmods add skills/nikuscs/codex-cc-plugin/claude-adversarial-reviewWrote 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/skills/nikuscs/codex-cc-plugin/claude-adversarial-review)<a href="https://agentmods.dev/skills/nikuscs/codex-cc-plugin/claude-adversarial-review"><img src="https://agentmods.dev/badge/skills/nikuscs/codex-cc-plugin/claude-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.00027 | $0.00094 |
| Opus 5 | $0.00014 | $0.00047 |
| Sonnet 5 | $0.00005 | $0.00019 |
| Haiku 4.5 | $0.00003 | $0.00009 |
Grade A, and why
claude-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 7d 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.
What it actually says
Claude Adversarial Review
Run the structured adversarial review flow.
This path accepts extra focus text and uses the adversarial review prompt template.
node plugins/claude/scripts/claude-companion.mjs adversarial-review --scope auto "Challenge the design tradeoffs."
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.
- 7d ago First seen · 15 lines · 27 tokens per session scan A 2d7f53b064ae
claude-adversarial-review is a skill published in the GitHub repository nikuscs/codex-cc-plugin (6 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 94 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 skills, from other repositories
source-owner-audit
Use for read-only source-of-truth audits: identify the current code, API, config, doc, or behavior to follow; compare a proposed, migrated, ported, or current change against it; and report evidence, mismatches, unresolved decisions, and owner-level recommendations.
structure-first
Use for code generation, feature work, bug fixes, refactoring, and code review when a change creates or reshapes a multi-step flow, state lifecycle, side-effect or decision ownership, cross-unit composition, or boundary contract. Also use it when an existing structural problem makes those elements hard to trace or…
grok-build-delegate
Use the local Grok Build CLI for second-opinion reviews, adversarial critiques, or delegated read-only investigation from Codex.
module-design
A lightweight method for improving how code is divided into modules, where modules are parts of a program with defined responsibilities.
sdlc-readiness-review
Use only when the user explicitly invokes this skill to make a readiness-gate judgment on SDLC materials, specs, handoffs, issues, or direct-dev requests.
dev-git-workflow
Use for non-trivial Git state such as branch strategy, worktrees, merge/rebase decisions, conflicts, reviewer-facing PR preparation, tags, and release notes. Do not trigger for a routine commit, push, or PR that needs no strategy decision.