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 raisedadead/claude-code-plugins --skill doubt-passgit clone --depth 1 https://github.com/raisedadead/claude-code-pluginsWrote 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/raisedadead/claude-code-plugins/doubt-pass)<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/doubt-pass"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/doubt-pass/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/raisedadead/claude-code-plugins/doubt-pass"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/doubt-pass.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.00070 | $0.00677 |
| Opus 5.5 | $0.00028 | $0.00271 |
| Sonnet 5.5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
doubt-pass 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 2d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
doubt-pass — break the plan before you build it
The cheapest bug is the one caught before the code exists. A fresh-context reviewer gets the plan and one job: find where it breaks, not whether it is nice. Bounded at three cycles, every finding classified, with a name for the case where doubt spins and lands nothing.
When to use
- Before a non-trivial architecture or design decision.
- The user asks for a plan to be stress-tested, holes poked, a second opinion — while it is still a plan, no diff yet.
Neighbours: /code-review needs a diff that already exists; whetstone:grill interviews you for requirements. This one sends a fresh agent at an artifact.
Protocol
Five steps, detailed in reference/doubt-protocol.md:
- CLAIM — state the decision in one paragraph.
- EXTRACT — strip it to an artifact plus a contract (inputs, outputs, invariants). Send those two; the reasoning trail stays behind, so the reviewer judges the design rather than your defence of it.
- DOUBT — spawn
whetstone-doubter(Agent,subagent_type: whetstone:whetstone-doubter) with the extracted artifact and contract as its whole input. The agent already carries the adversarial method — "find where this breaks" — and its word budget;reference/adversarial-prompt-template.mdis the mission text to fill and send. It returnsDOUBT: FAILURESorNO FAILURE FOUND. - RECONCILE — tag every returned finding
actionableornot-actionable, each on its own merits. - STOP — at the 3-cycle cap, or at the first cycle that returns nothing new. Fold actionable findings into the plan between cycles.
Doubt theater
Zero cumulative actionable findings across every cycle is its own result. Report it as one:
doubt theater — N findings raised, 0 actionable across M cycles. Escalate to a human or ship as-is.
Cycling a reviewer that lands nothing is motion. Naming it keeps it from reading as confidence.
Verification
Done = the loop stopped at ≤ 3 cycles, every finding carries an actionable / not-actionable tag, and the outcome is one of: plan amended with the actionable findings, or an explicit doubt theater note. The cap and the classification are the gate; "let me think about it more" is a different activity.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed 66a94a505733
- 1mo ago First seen · 44 lines · 70 tokens per session scan A 935403c8cf34
doubt-pass is a skill published in the GitHub repository raisedadead/claude-code-plugins (3 stars, last pushed today), licensed ISC. It adds 70 tokens to every session and 677 once invoked, about $0.0003 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-31.
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…