epistemic-challenge

epistemic-challenge is a skill for Claude Code from AnastasiyaW/codex-claude-code-config. It costs 77 tokens per session (988 once invoked), scanned A, original, MIT.

A guide for examining assumptions and decisions using facts, inferences, uncertainty, opposing evidence, and conditions that could prove the conclusion wrong.

In plain words
What is it for?
Use it when reviewing proposals, researching disputed claims, challenging assumptions, or making high-consequence decisions with incomplete information.
Why use it?
It reduces the risk of agreeing with an unsupported idea or making an important decision without considering evidence against it.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the claude-code-config plugin — 57 skills, 8 agents shipped together

Good fit Use it when reviewing proposals, researching disputed claims, challenging assumptions, or making high-consequence decisions with incomplete information.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anastasiyaw/codex-claude-code-config/epistemic-challenge
Install

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.

Any agent
npx skills add AnastasiyaW/codex-claude-code-config --skill epistemic-challenge
Clone the repo
git clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-config

Made for: Claude Code.

Or install claude-code-config, the plugin that ships this one along with the rest of its 57 skills, 8 agents.

Wrote 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.

agentmods badge for epistemic-challenge

README.md
[![agentmods](https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/epistemic-challenge/github.svg)](https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/epistemic-challenge)
Your own site
<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/epistemic-challenge"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/epistemic-challenge/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.

agentmods 80×15 button for epistemic-challenge

Your own site · 80×15
<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/epistemic-challenge"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/epistemic-challenge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 988 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.00988
Opus 5 $0.00039 $0.00494
Sonnet 5 $0.00015 $0.00198
Haiku 4.5 $0.00008 $0.00099

Measured 10d ago against content hash abb6999fc185, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

epistemic-challenge 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 10d 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.

skills/operational/epistemic-challenge/SKILL.md · 90 lines

How it starts

The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Epistemic Challenge

Purpose

Give evidence-bound disagreement when it is warranted, and evidence-bound agreement when it is warranted. The goal is not a "devil's advocate" persona: invented opposition is as misleading as automatic agreement.

When to use

Use for an explicit request for critical independence, a factual premise that would change an implementation or decision, a disputed conclusion, research, or an important recommendation. Do not apply the full protocol to a simple instruction, a preference the user owns, or a fact directly measured in the current tool result.

Procedure

  1. State the operative claim or decision in a falsifiable form. Separate a user preference (which needs no fact-check) from an empirical claim (which does).
  2. Collect source-backed evidence before giving a verdict. First prefer a current local observation (code, log, probe) or primary documentation; an explicit user constraint is evidence for a value choice. Memory and prior assistant text are only search leads and must be re-checked before they support a current factual claim. User confidence and a pleasing narrative are not evidence.
  3. Name the strongest realistic counter-hypothesis and the observation that distinguishes it from the proposed explanation. Do not create a weak counterargument merely to sound critical.
  4. For research or a consequential decision, verify the discriminator without showing the checker the proposed conclusion when practical. Prefer a fresh reviewer for destructive, production, financial, security, or architectural actions.
  5. Return one of: SUPPORTED, REFUTED, INCONCLUSIVE, or VALUE_CHOICE. Say what would change the verdict. Change a conclusion only for new evidence or a corrected inference, not because the user repeats a preference or asks "are you sure?".

Output contract

For a substantive claim, use this compact shape:

Verdict: SUPPORTED | REFUTED | INCONCLUSIVE | VALUE_CHOICE
Evidence: [observed source or command result]
Counterevidence / alternative: [strongest live alternative, or none found]
Boundary: [what was not established]
Next falsifier: [one observation that would change the verdict]

Read the full file on GitHub · 90 lines

Changes

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.

  1. 10d ago First seen · 90 lines · 77 tokens per session scan A abb6999fc185

Subscribe to this mod's changes

epistemic-challenge is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed yesterday), licensed MIT. It adds 77 tokens to every session and 988 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-08-30.