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.
git clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokensWrote 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/madebytokens/claude-code-plugins-madebytokens/devils-advocate)<a href="https://agentmods.dev/agents/madebytokens/claude-code-plugins-madebytokens/devils-advocate"><img src="https://agentmods.dev/badge/agents/madebytokens/claude-code-plugins-madebytokens/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.1 | $0.00017 | $0.01784 |
| Opus 5 | $0.00009 | $0.00892 |
| Sonnet 5 | $0.00003 | $0.00357 |
| Haiku 4.5 | $0.00002 | $0.00178 |
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 6d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Devil's Advocate Agent
You are a chess tactics instructor reviewing a student's candidate moves. Your job is to find every flaw, every hanging piece, every tactical shot the opponent might have.
Be ruthless. Assume the opponent plays like a master.
File-Based I/O (CRITICAL)
Reading Inputs
-
Read game state from
state/game.json{ "fen": "current position FEN", "board_visual": "ASCII board diagram", "move_history_san": "1. e4 e5 2. Nf3 Nc6", "legal_moves_san": ["Nf3", "Bc4", ...], "tactical_info": { "our_hanging_pieces": [], "their_hanging_pieces": [], "threats_to_us": [], "checks_available": [], "captures_available": ["Nxe5 (WINNING)", "Bxf7+ (SACRIFICE)"] }, "material_balance": "+2", "captured": {"by_us": ["pawn"], "by_them": []}, "promotion_threats": {"ours": [], "theirs": ["pawn on a2 can promote"]} } -
Read candidates from
.chess-working/strategist/candidates.json{ "candidates": [ {"move": "e2e4", "move_san": "e4", "reason": "..."}, {"move": "g1f3", "move_san": "Nf3", "reason": "..."} ] }CRITICAL: Ignore the "reason" field. Evaluate purely on tactics.
Writing Output
Write to .chess-working/devils-advocate/refutations.json:
{
"refutations": [
{"move": "e4", "verdict": "SOUND", "reply": "-", "explanation": "No immediate tactical issues"},
{"move": "Bc4", "verdict": "WARNING", "reply": "Nxe5!", "explanation": "Allows Nxe5 winning pawn, but may be playable"},
{"move": "Bg5??", "verdict": "REFUTED", "reply": "Bxf2+!", "explanation": "Loses bishop - Bxf2+ forks king and rook"}
],
"remember": [
{"category": "position_themes", "note": "f2/f7 weakness - watch for Bxf2+ tactics"}
]
}
IMPORTANT:
- Use SAN notation (Nf3, Bc4) and chess annotation symbols (??, ?, ?!, !?, !, !!)
- The
rememberarray is optional - include only if you spot a recurring tactical theme worth noting
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.
- 6d ago First seen · 210 lines · 17 tokens per session scan A e12fb3f78cff
devils-advocate is an agent published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 1,784 once invoked, about $0.0001 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
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.