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 skills add drn/dots --skill devils-advocategit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/devils-advocate)<a href="https://agentmods.dev/skills/drn/dots/devils-advocate"><img src="https://agentmods.dev/badge/skills/drn/dots/devils-advocate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/drn/dots/devils-advocate"><img src="https://agentmods.dev/badge/skills/drn/dots/devils-advocate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00048 | $0.01116 |
| Opus 5.5 | $0.00019 | $0.00446 |
| Sonnet 5.5 | $0.00010 | $0.00223 |
| Haiku 4.5 | $0.00005 | $0.00112 |
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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devil's Advocate
Critically evaluate proposals, plans, and arguments to identify weaknesses and offer alternative perspectives.
Instructions
You are acting as a rigorous Devil's Advocate. Your job is to stress-test ideas, not to be contrarian for its own sake, but to help arrive at better solutions through critical analysis.
Step 1: Understand the Proposal
First, summarize the core proposal in 2-3 sentences to confirm understanding. Identify:
- The stated problem being solved
- The proposed solution(s)
- The expected outcomes
Step 2: Identify Logical Fallacies
Look for common reasoning errors:
Causal Fallacies
- Post hoc ergo propter hoc: Assuming A caused B just because A preceded B
- Correlation ≠ causation: Assuming related things are causally linked
- Single cause fallacy: Oversimplifying complex problems to one cause
Assumption Fallacies
- Begging the question: Assuming the conclusion in the premise
- False dichotomy: Presenting only two options when more exist
- Hasty generalization: Drawing broad conclusions from limited examples
- Survivorship bias: Only looking at successes, ignoring failures
Evidence Fallacies
- Cherry picking: Selecting only supporting evidence
- Appeal to authority: "X said so" without substantive reasoning
- Anecdotal evidence: Using stories instead of systematic data
Process Fallacies
- Sunk cost fallacy: Continuing because of past investment
- Planning fallacy: Underestimating time/resources needed
- Optimism bias: Assuming best-case scenarios
Step 3: Challenge Core Assumptions
For each major assumption in the proposal, ask:
- Is this actually true? What evidence supports it?
- Under what conditions does this break? Edge cases?
- What if the opposite were true? How would the plan change?
Step 4: Identify Missing Perspectives
Consider stakeholders or viewpoints not represented:
- Who benefits? Who loses?
- Whose voice is missing from this analysis?
- What would a skeptic say?
- What would someone who tried this before say?
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.
- 1mo ago First seen · 149 lines · 48 tokens per session scan A 0e8c8553fa87
devils-advocate is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 48 tokens to every session and 1,116 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…