fact-check

fact-check is a skill for Claude Code, Codex from jezweb/vite-flare-starter. It costs 36 tokens per session (457 once invoked), scanned A, original, MIT.

A skill for checking a specific factual claim against multiple authoritative sources.

In plain words
What is it for?
Use it to verify claims, find sources that confirm or contradict them, and report whether the claim is confirmed, partly true, or false.
Why use it?
It reduces the risk of accepting an unsupported or misleading statement by comparing independent evidence.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to verify claims, find sources that confirm or contradict them, and report whether the claim is confirmed, partly true, or false.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jezweb/vite-flare-starter/fact-check
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 jezweb/vite-flare-starter --skill fact-check
Clone the repo
git clone --depth 1 https://github.com/jezweb/vite-flare-starter

Made for: Claude Code, Codex.

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-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/fact-check/github.svg)](https://agentmods.dev/skills/jezweb/vite-flare-starter/fact-check)
Your own site
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/fact-check"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/fact-check/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-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/fact-check"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/fact-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 457 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.00036 $0.00457
Opus 5 $0.00018 $0.00229
Sonnet 5 $0.00007 $0.00091
Haiku 4.5 $0.00004 $0.00046

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

Security

Grade A, and why

fact-check 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/fact-check/SKILL.md · 47 lines

What it actually says

Fact Check

When to use

The user has stated a specific claim and wants to know if it's accurate. Examples:

  • "Is it true that X?"
  • "Fact-check this: ..."
  • "Did Y actually happen?"

Steps

  1. Identify the claim — extract the precise factual assertion. If the claim is fuzzy ("apparently X is good"), use ask_questions to nail down what specifically to verify.

  2. Search for primary sources — use web_search with the claim phrased neutrally. Look for:

    • Official sources (government sites, academic papers, the organisation involved)
    • Reputable journalism (major outlets with editorial standards)
    • Primary data (statistics agencies, public records)
  3. Avoid these as sole sources:

    • Social media posts (use only as leads to follow up)
    • Single-source blogs without citations
    • Anything that quotes the claim back without independent verification
  4. Cross-reference — find at least 2-3 independent sources. If they all trace back to one origin, you only have one source.

  5. Report verdict — use show_alert with the appropriate type:

    • success — Confirmed (multiple authoritative sources agree)
    • warning — Partly true / context needed
    • error — False (sources contradict the claim)
    • info — Unverifiable (insufficient evidence either way)
  6. Provide evidence — list the sources with what each one says. Use markdown links.

Style

  • Be neutral. Avoid editorialising.
  • Distinguish "X is false" from "I couldn't find evidence for X" — these are different.
  • If the claim is partly true, be specific about which parts.

What not to do

  • Don't trust a single source, even an authoritative one, for contested claims.
  • Don't conflate "common knowledge" with verified fact.
  • Don't fabricate confidence — uncertainty is a valid finding.
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 · 47 lines · 36 tokens per session scan A 851492bc19dd

Subscribe to this mod's changes

fact-check is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 15d ago), licensed MIT. It adds 36 tokens to every session and 457 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens