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/xrensiu/claude-code-forge/adversarial-requirementsnpx skills add XRenSiu/claude-code-forge --skill adversarial-requirementsgit clone --depth 1 https://github.com/XRenSiu/claude-code-forgeWrote 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/xrensiu/claude-code-forge/adversarial-requirements)<a href="https://agentmods.dev/skills/xrensiu/claude-code-forge/adversarial-requirements"><img src="https://agentmods.dev/badge/skills/xrensiu/claude-code-forge/adversarial-requirements.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.00116 | $0.03744 |
| Opus 5 | $0.00058 | $0.01872 |
| Sonnet 5 | $0.00023 | $0.00749 |
| Haiku 4.5 | $0.00012 | $0.00374 |
Grade A, and why
adversarial-requirements 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.
How it starts
The opening of the file, as written. The whole thing — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adversarial Requirements
用两个 agent 的对抗辩论替代单人闭门造车的需求文档。
实测数据:单人撰写的 PRD 平均有 3-5 个技术可行性盲点。对抗式需求通过产品倡导者 + 技术怀疑者的结构化辩论,将需求文档的技术可行性问题提前暴露,减少 60%+ 的实现阶段返工。
Announce at start: "I'm using the adversarial-requirements skill to create a battle-tested PRD through product-technical debate."
前置条件: 需要启用 Agent Teams 实验性功能。 在 settings.json 中添加:
"env": { "CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1" }
When to Use
digraph {
rankdir=TB;
start [label="新功能需求" shape=oval];
q1 [label="需求复杂度?" shape=diamond];
q2 [label="技术风险?" shape=diamond];
simple_prd [label="单 agent PRD\n(常规流程)" shape=box];
adversarial [label="adversarial-requirements\n(本 Skill)" shape=box style=filled fillcolor=lightgreen];
start -> q1;
q1 -> simple_prd [label="低\n明确的需求"];
q1 -> q2 [label="中/高"];
q2 -> simple_prd [label="低"];
q2 -> adversarial [label="中/高"];
}
The 7-Step Protocol
┌─────────────────────────────────────────────────────────────────┐
│ ADVERSARIAL REQUIREMENTS │
├─────────────────────────────────────────────────────────────────┤
│ │
│ Step 1: INTAKE 收集用户需求描述 │
│ ↓ │
│ │
│ Step 2: TEAM CREATE 创建 Agent Team │
│ ↓ Product Advocate + Technical Skeptic │
│ │
│ Step 3: ADVOCATE DRAFT 产品倡导者分析代码库 + 撰写 PRD 草案 │
│ ↓ │
│ │
│ Step 4: SKEPTIC CHALLENGE 技术怀疑者分析代码库 + 挑战 PRD │
│ ↓ │
│ │
│ Step 5: DEBATE 倡导者回应 + 怀疑者再挑战 (2 轮) │
│ ↓ │
│ │
│ Step 6: SYNTHESIS Lead 综合产出 battle-tested PRD │
│ ↓ │
│ │
│ Step 7: CLEANUP Shutdown Team + 输出最终文档 │
│ │
└─────────────────────────────────────────────────────────────────┘
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 · 456 lines · 116 tokens per session scan A a2294ee2ed68
adversarial-requirements is a skill published in the GitHub repository XRenSiu/claude-code-forge (2 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 3,744 once invoked, about $0.0006 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…