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 skills/wrannaman/agentic-engineering/adversarialnpx skills add wrannaman/agentic-engineering --skill adversarialgit clone --depth 1 https://github.com/wrannaman/agentic-engineeringWrote 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/wrannaman/agentic-engineering/adversarial)<a href="https://agentmods.dev/skills/wrannaman/agentic-engineering/adversarial"><img src="https://agentmods.dev/badge/skills/wrannaman/agentic-engineering/adversarial.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.00054 | $0.01032 |
| Opus 5 | $0.00027 | $0.00516 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
adversarial-brainstorm 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 3d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adversarial Brainstorming
Overview
Pressure-test ideas and designs through adversarial analysis before implementation.
Find what can fail, how it fails, and what safeguards are needed. Prioritize discovering hidden assumptions, edge cases, abuse paths, operational risks, and rollback gaps.
Anti-Pattern: "Happy Path Means Safe"
Treat all designs as vulnerable until challenged. "Simple" changes still need failure-mode analysis because small assumptions cause large regressions.
Checklist
You MUST create a task for each of these items and complete them in order:
- Explore project context deeply — check files, docs, recent commits
- Clarify assumptions — ask one question at a time about constraints, trust boundaries, and success criteria
- Generate challenge models — propose 2-3 adversarial lenses with trade-offs and recommendation
- Stress-test the design — identify edge cases, failure modes, abuse paths, and operational hazards
- Present adversarial review — show findings and mitigations in sections scaled to complexity, get user approval after each section
- Write adversarial design doc — save to
<agent-settings-directory(.claude|.agents|.codex)>/plans/YYYY-MM-DD-<topic>-adversarial-design.mdand commit - Transition to implementation planning — invoke plan skill
Process Flow
digraph adversarial_brainstorming {
"Explore project context" [shape=box];
"Clarify assumptions" [shape=box];
"Propose challenge models" [shape=box];
"Stress-test design" [shape=box];
"Present findings + mitigations" [shape=box];
"User approves mitigations?" [shape=diamond];
"Write adversarial design doc" [shape=box];
"Invoke plan skill" [shape=doublecircle];
"Explore project context" -> "Clarify assumptions";
"Clarify assumptions" -> "Propose challenge models";
"Propose challenge models" -> "Stress-test design";
"Stress-test design" -> "Present findings + mitigations";
"Present findings + mitigations" -> "User approves mitigations?";
"User approves mitigations?" -> "Present findings + mitigations" [label="no, revise"];
"User approves mitigations?" -> "Write adversarial design doc" [label="yes"];
"Write adversarial design doc" -> "Invoke plan skill";
}
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.
- 3d ago First seen · 96 lines · 54 tokens per session scan A be4a6012553e
adversarial-brainstorm is a skill published in the GitHub repository wrannaman/agentic-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 54 tokens to every session and 1,032 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…