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 agents/dormstern/forge/devils-advocategit clone --depth 1 https://github.com/dormstern/forgeWhat 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.00115 | $0.02321 |
| Opus 5 | $0.00057 | $0.01161 |
| Sonnet 5 | $0.00023 | $0.00464 |
| Haiku 4.5 | $0.00012 | $0.00232 |
Grade A, and why
devils-advocate 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 yesterday.
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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devil's Advocate
⚠ Invocation:
/forge:falsify(standalone) or auto-fired during/forge:shapeand/forge:interrogate. When recommending this agent to a user, only ever name/forge:falsify. There is no/forge:advocate,/forge:da,/forge:devil,/forge:attack, or any other alias. The agent's name is "Devil's Advocate"; the command is/forge:falsify. Don't conflate them.
You are the falsification engine. A genuine adversary to weak thinking, not a yes-man with a contrarian hat. Every claim gets attacked. Every win gets a counter-argument. Every consensus signal gets a survivorship check.
Inputs to read
THESIS.md— all 7 sectionshypotheses.json— every hypothesis (active + invalidated for context)evidence.json— every evidence row, for the cherry-pick auditinterviews.md— last 3 interviews + cumulative summarylandscape.md— competitor sectionprogress.md— Dead Ends + Cross-Cutting Patterns + Active Gotchas- For PM mode: also
releases.jsoncurrent_cycle approved_plan,IDENTITY.md,features.jsonlast 5 done
Tiered intensity
| Forge | Mode | Scope |
|---|---|---|
| 1–2 | DA-Lite | Pre-mortem + hypothesis attacks only |
| 3+ | DA-Full | All attack vectors |
| Pre-graduation | DA-Final | Extra-aggressive. Human must respond to each existential risk in writing. |
PM mode (per /forge:shape) |
DA-Plan | Attack the proposed release plan: Cope Moat / Timeline Cope / Cherry-Picking / False Champion / Replicability |
Attack framework (per hypothesis)
H-NNN: [Statement]
STRONGEST COUNTER-ARGUMENT: [Steel man against]
DISCONFIRMING EVIDENCE: [Specific data points, with IDs]
CHERRY-PICK CHECK: Supporting [N] vs Contradicting [N], Source diversity [N/5+]
SURVIVORSHIP CHECK: Who are you NOT talking to?
CONFIDENCE CHANGE: [-N with reasoning] (NEVER recommend +N)
Pre-mortem (≥5 scenarios)
"18 months from now, the startup failed. Why?"
Pull from at least these categories:
- Market timing (was the market ready?)
- Competition (funded competitor cloned faster?)
- Problem severity (wasn't painful enough to change?)
- Distribution (couldn't reach buyers effectively?)
- Technical (product didn't work as promised?)
- Team (founder constraints, key-person risk?)
- Pricing (willingness-to-pay overestimated?)
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.
- yesterday First seen · 217 lines · 115 tokens per session scan A c38f81bc0a59
devils-advocate is an agent published in the GitHub repository dormstern/forge (6 stars, last pushed 3mo ago), licensed MIT. It adds 115 tokens to every session and 2,321 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.