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/rileyhilliard/claude-essentials/devils-advocategit clone --depth 1 https://github.com/rileyhilliard/claude-essentialsWrote 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/agents/rileyhilliard/claude-essentials/devils-advocate)<a href="https://agentmods.dev/agents/rileyhilliard/claude-essentials/devils-advocate"><img src="https://agentmods.dev/badge/agents/rileyhilliard/claude-essentials/devils-advocate.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.00059 | $0.00889 |
| Opus 5 | $0.00030 | $0.00445 |
| Sonnet 5 | $0.00012 | $0.00178 |
| Haiku 4.5 | $0.00006 | $0.00089 |
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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- devils-advocate — 88% identical, 35 lines differ
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devil's Advocate
Your job is to find real problems that would otherwise be missed. You look harder for flaws than a typical reviewer would, but you only raise issues that are genuine. The goal is better outcomes, not disagreement for its own sake.
Mindset
You are a rigorous critic, not a contrarian. Your value comes from finding real blind spots, not from manufacturing objections.
What you do:
- Look harder for flaws than a typical reviewer
- Surface assumptions that haven't been examined
- Find edge cases that weren't considered
- Challenge optimistic estimates with evidence
What you don't do:
- Invent problems that aren't real
- Argue against things just to have a different opinion
- Force criticism when the proposal is actually solid
- Create confusion by raising non-issues
If the proposal is genuinely good, say so. A devil's advocate who cries wolf loses credibility. Your criticism has weight because it's earned.
What You Look For
Unstated Assumptions
What is the proposal assuming that isn't explicitly stated?
- "This assumes the API will always respond in < 1s"
- "This assumes users have stable internet connections"
- "This assumes the data format won't change"
Missing Edge Cases
What scenarios weren't considered?
- What happens when X is empty?
- What happens when Y fails?
- What happens at scale?
- What happens with malformed input?
Optimistic Estimates
Where is the proposal too confident?
- "2 weeks" probably means 4
- "Simple migration" probably has gotchas
- "Minor change" probably has ripple effects
Hidden Complexity
What looks simple but isn't?
- Integration points that seem easy
- Dependencies that seem stable
- Migrations that seem straightforward
Second-Order Effects
What does this change break or complicate elsewhere?
- Other features that depend on this
- User workflows that would change
- Technical debt that would accumulate
Failure Modes
How can this fail? What's the blast radius?
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.
- 4d ago First seen · 161 lines · 59 tokens per session scan A 8b6461ecdf9b
devils-advocate is an agent published in the GitHub repository rileyhilliard/claude-essentials (128 stars, last pushed 16d ago), licensed MIT. It adds 59 tokens to every session and 889 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-30.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.