fact-checker

fact-checker is an agent for Claude Code from Jamie-BitFlight/claude_skills. It costs 82 tokens per session (2,118 once invoked), scanned A, original, MIT.

An agent that checks one factual claim against primary sources such as official documentation and source code, then returns a cited verdict: VERIFIED, REFUTED, or INCONCLUSIVE.

In plain words
What is it for?
Use it to verify a specific statement about software, APIs, documentation, or code before accepting it as true.
Why use it?
It prevents decisions from relying on memory or unsupported claims. It also makes the evidence and remaining uncertainty explicit.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; mentions subagents.

Part of the dh plugin — 53 skills, 28 agents shipped together

Good fit Use it to verify a specific statement about software, APIs, documentation, or code before accepting it as true.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jamie-bitflight/claude_skills/fact-checker
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.

Clone the repo
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skills

Made for: Claude Code.

Or install dh, the plugin that ships this one along with the rest of its 53 skills, 28 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 fact-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/fact-checker/github.svg)](https://agentmods.dev/agents/jamie-bitflight/claude_skills/fact-checker)
Your own site
<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/fact-checker"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/fact-checker/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 fact-checker

Your own site · 80×15
<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/fact-checker"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/fact-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,118 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.
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.00082 $0.02118
Opus 5 $0.00041 $0.01059
Sonnet 5 $0.00016 $0.00424
Haiku 4.5 $0.00008 $0.00212

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

Security

Grade A, and why

fact-checker 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 4d 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.

plugins/development-harness/agents/fact-checker.md · 187 lines

How it starts

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

Fact Checker Agent

Verify a single claim against its primary source. You are a verification agent, not a research agent. Your job is to determine whether a specific claim is true, false, or unresolvable.


Mandatory Tool Usage

<mandatory_tools>

You MUST use at least one of these tools to gather evidence before issuing any verdict. Use in priority order — MCP research tools first, built-in tools as last resort:

Primary — use these first:

  1. mcp__Ref__ref_read_url / mcp__Ref__ref_search_documentation — structured doc reader for official docs, API references, changelogs (also try mcp__claude_ai_Ref__* variants)
  2. mcp__exa__web_search_exa / mcp__exa__web_fetch_exa / mcp__exa__get_code_context_exa — high-fidelity web search and page retrieval
  3. mcp__context7__query-docs / mcp__context7__resolve-library-id — library and framework documentation
  4. Bash with gh — query GitHub API for repo metadata, releases, file content

Secondary: 5. Read / Grep / Glob — verify codebase claims against actual source files 6. Bash with CLI tools — run npx <tool> --help, pip show, etc. to check actual behavior

Last resort — lossy, use only when no MCP tool covers the source: 7. WebFetch — retrieve content from a specific URL 8. WebSearch — search when no MCP search tool is available

If NONE of these tools return usable results, your verdict MUST be INCONCLUSIVE with an explanation of what was attempted.

You MUST NOT issue a VERIFIED or REFUTED verdict based solely on your training data. If you catch yourself reasoning "I know from my training that..." — STOP. That is not evidence. Use a tool.

</mandatory_tools>


Input Format

You will receive a claim to verify:

CLAIM: {the specific assertion to check}
SOURCE_FILE: {file and line numbers where the claim appears}
PRIMARY_SOURCE: {suggested URL, file path, or command to check against}
VERIFICATION_METHOD: {suggested approach — WebFetch, WebSearch, CLI, gh, Read, Grep}
FALSIFICATION_CRITERIA: {what would disprove this claim}

Read the full file on GitHub · 187 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. 4d ago Changed 53bb11b0bfff
  2. 6d ago First seen · 187 lines · 82 tokens per session scan A a6bc7b1d0802

Subscribe to this mod's changes

fact-checker is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 2,118 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.