fact-check

fact-check is a skill for Claude Code, Codex from LeeJuOh/claude-code-zero. It costs 51 tokens per session (3,729 once invoked), scanned A, original, MIT.

A fact-checking skill that compares claims in a document with the codebase and Git history. Git history is the record of earlier changes to the project.

In plain words
What is it for?
Use it to verify reports or documents, correct inaccurate claims in place, and add a verification summary in HTML or Markdown.
Why use it?
It helps correct statements that do not match the actual implementation or project history without changing the document's overall structure.

Skill for Claude CodeCodex

Part of the vision-powers plugin — 4 skills, 4 agents shipped together

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.

agentmods
npx agentmods add skills/leejuoh/claude-code-zero/fact-check
Any agent
npx skills add LeeJuOh/claude-code-zero --skill fact-check
Clone the repo
git clone --depth 1 https://github.com/LeeJuOh/claude-code-zero

Made for: Claude Code, Codex.

Or install vision-powers, the plugin that ships this one along with the rest of its 4 skills, 4 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-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/leejuoh/claude-code-zero/fact-check.svg)](https://agentmods.dev/skills/leejuoh/claude-code-zero/fact-check)
Your own site
<a href="https://agentmods.dev/skills/leejuoh/claude-code-zero/fact-check"><img src="https://agentmods.dev/badge/skills/leejuoh/claude-code-zero/fact-check.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,729 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00051 $0.03729
Opus 5 $0.00026 $0.01865
Sonnet 5 $0.00010 $0.00746
Haiku 4.5 $0.00005 $0.00373

Measured 3d ago against content hash 8f4edd6757ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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/vision-powers/skills/fact-check/SKILL.md · 279 lines

How it starts

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

Fact Check

Verify the factual accuracy of a document against the actual codebase and git history. Extracts verifiable claims, checks each against source, corrects inaccuracies in place, and adds a verification summary.

This is not a re-review. It does not second-guess analysis, opinions, or design judgments. It does not change the document's structure or organization. It is a fact-checker — it verifies that the data presented matches reality, corrects what doesn't, and leaves everything else alone.

Instructions

Format Detection

--format controls which verification-summary block to inject:

Flag Values Default Meaning
--format html | md auto Auto-detected from the input file extension (.html → html block, .md → markdown block). Override when the input is a generic text file or when you want a markdown summary inside an HTML document

Principle: Fact-check edits the source document in place. The format flag only governs the verification summary appended at the end — HTML summary uses KPI cards + <details> blocks, markdown summary uses a table + bullet lists. Auto-detection is almost always correct; override only for edge cases.

Target File Detection

Determine what to verify from $1:

  1. Explicit path: Verify that specific file (.html, .md, or any text document)
    • Resolve relative paths against cwd
  2. No argument: Auto-detect the most recent report of either format:
    ls -t ${CLAUDE_PLUGIN_DATA}/reports/*.html ${CLAUDE_PLUGIN_DATA}/reports/*.md 2>/dev/null | head -1
    
    If no reports found, inform the user and stop.

Document type detection — auto-detect from page content to adjust verification strategy:

Document Type Detection Verification Focus
diff-visual report Contains "Diff Visual" in title/heading Verify against the git ref the review was based on
doc-visual report Contains "Doc Visual" in title/heading Verify file references, names, architecture claims
plugin-visual report Contains plugin analysis markers Verify plugin structure, file paths, feature descriptions
Markdown document .md extension Verify file references, function/type names, behavior descriptions
Other Fallback Extract and verify whatever factual claims about code it contains

Read the full file on GitHub · 279 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. 3d ago First seen · 279 lines · 51 tokens per session scan A 8f4edd6757ba

Subscribe to this mod's changes

fact-check is a skill published in the GitHub repository LeeJuOh/claude-code-zero (51 stars, last pushed 4d ago), licensed MIT. It adds 51 tokens to every session and 3,729 once invoked, about $0.0003 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

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens