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 zhaixin244-wq/fnw --skill devils-advocategit clone --depth 1 https://github.com/zhaixin244-wq/fnwWrote 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/zhaixin244-wq/fnw/devils-advocate)<a href="https://agentmods.dev/skills/zhaixin244-wq/fnw/devils-advocate"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/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/zhaixin244-wq/fnw/devils-advocate"><img src="https://agentmods.dev/badge/skills/zhaixin244-wq/fnw/devils-advocate.svg" alt="Reviewed on agentmods" width="80" 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.00087 | $0.02818 |
| Opus 5 | $0.00044 | $0.01409 |
| Sonnet 5 | $0.00017 | $0.00564 |
| Haiku 4.5 | $0.00009 | $0.00282 |
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 9d 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 — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devil's Advocate
A structured critique skill that challenges decisions, plans, architecture, and code by systematically arguing the opposing side. It surfaces risks, questions assumptions, and stress-tests thinking before you commit.
When to Use This Skill
Use this skill when:
- The user invokes
/devils-advocatewith optional arguments - The user asks you to "challenge this", "poke holes in this", "what could go wrong", or "play devil's advocate"
- The user wants a critical review of a plan, architecture decision, or product strategy
- The user wants to stress-test an approach before committing
Invocation Format
/devils-advocate [severity] [file_path]
- severity (optional):
gentle,balanced,ruthless, orlinus. Defaults tobalanced. - file_path (optional): Path to a file or document to critique. If omitted, challenge the current conversation context.
Argument Parsing Rules
- If the first argument is one of
gentle,balanced,ruthless, orlinus, treat it as the severity level - Any remaining argument is treated as a file path
- If only one argument is given and it's NOT a severity keyword, treat it as a file path with
balancedseverity - If no arguments are given, use
balancedseverity against the current conversation context
Examples:
/devils-advocate- balanced critique of conversation context/devils-advocate gentle- gentle critique of conversation context/devils-advocate ruthless src/auth/strategy.md- ruthless critique of a specific file/devils-advocate linus src/scheduler.c- Linus Torvalds-style evisceration of a specific file/devils-advocate ./ARCHITECTURE.md- balanced critique of a specific file
Severity Levels
gentle - Constructive Skeptic
- Acknowledge strengths and good decisions first
- Raise 2-3 key concerns with concrete counter-proposals
- Frame objections as questions rather than accusations
- Include a supportive verdict at the end
- Tone: collaborative, encouraging, "yes, and..."
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.
- 9d ago First seen · 274 lines · 87 tokens per session scan A 383f43ab574c
devils-advocate is a skill published in the GitHub repository zhaixin244-wq/fnw (29 stars, last pushed 3mo ago), licensed MIT. It adds 87 tokens to every session and 2,818 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.