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 instructions/brandonsimpson/devils-advocate/claude-mdgit clone --depth 1 https://github.com/brandonsimpson/devils-advocateWrote 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/instructions/brandonsimpson/devils-advocate/claude-md)<a href="https://agentmods.dev/instructions/brandonsimpson/devils-advocate/claude-md"><img src="https://agentmods.dev/badge/instructions/brandonsimpson/devils-advocate/claude-md.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.00277 | $0.00277 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
devils-advocate CLAUDE.md 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 5d 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.
What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Structure
This repo has two layers:
- Repo root — Marketplace registry (
.claude-plugin/marketplace.json) plus README, LICENSE, and banner plugin/— The actual plugin (skills, hooks, scripts, metadata)
The marketplace points to the plugin via "source": "./plugin". This separation prevents the circular cache loop that occurs when a marketplace and plugin share the same directory.
Getting Started
See plugin/CLAUDE.md for full project documentation including architecture, conventions, and how to validate changes.
Quick Reference
- Run consistency checks:
bash plugin/scripts/check-consistency.sh(supports--quiet) - Run test suite:
bash plugin/scripts/test-plugin.sh(supports--quiet) - Run LLM evals (after any SKILL.md change):
bash plugin/scripts/eval.sh— liveclaude -pcalls, ~2-5 min, costs tokens - Test locally:
claude --plugin-dir ./plugin - Version source of truth:
plugin/.claude-plugin/plugin.json(must stay in sync with.claude-plugin/marketplace.json)
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.
- 5d ago First seen · 25 lines · 277 tokens per session scan A 5c17d0ca91a0
devils-advocate CLAUDE.md is an instructions file published in the GitHub repository brandonsimpson/devils-advocate (22 stars, last pushed 2mo ago), licensed MIT. It adds 277 tokens to every session, about $0.0014 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 instructions, from other repositories
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.