What is validate-facts?

A resume fact-checker that compares claims in a resume with records supporting the candidate’s experience. It produces a report marking claims as supported, unsupported, or contradicted.

Use it to verify a resume before changing its keywords or terminology. It requires a parsed resume and candidate evidence records.

It helps prevent inaccurate resume claims from being carried into later edits. The checks use saved evidence and do not require an AI language model.

validate-facts — Skill for Claude Code and Codex by dcassil: A resume fact-checker that compares claims in a resume…

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/dcassil/resume-kit/validate-facts

Any agent

npx skills add dcassil/resume-kit --skill validate-facts

Clone the repo

git clone --depth 1 https://github.com/dcassil/resume-kit

Made for: Claude Code, Codex.

Or install resume-intelligence, the plugin that ships this one along with the rest of its 31 skills, 1 command, 1 hook.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dcassil/resume-kit/validate-facts.svg)](https://agentmods.dev/skills/dcassil/resume-kit/validate-facts)

Your own site

<a href="https://agentmods.dev/skills/dcassil/resume-kit/validate-facts"><img src="https://agentmods.dev/badge/skills/dcassil/resume-kit/validate-facts.svg" alt="Measured on agentmods" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 756 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.

Model	Per session	Once invoked
Fable 5	$0.00032	$0.00756
Opus 5	$0.00016	$0.00378
Sonnet 5	$0.00006	$0.00151
Haiku 4.5	$0.00003	$0.00076

Measured 4d ago against content hash 26e58ecf2bce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

validate-facts 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/resume-intelligence/skills/validate-facts/SKILL.md · 84 lines

How it starts

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

Renamed: validate-facts was validate-resume-truth before v1.0.0 (see RIT-A-0005).

Inputs must be canonical JSON. This capability consumes a resume as a ResumeDocument JSON (build it from a PDF/DOCX/MD/text file with the parse-resume skill) and, where a job is involved, a JobDescription JSON (build it with parse-job so skills-coverage scoring works). Run those conversions in subagents, then pass the saved JSON paths here — they live under resume-kit/resumes/ and resume-kit/jobs/.

Prerequisites

Run the shared Prerequisites gate first — see _shared/prerequisites.md.

Required inputs: a ResumeDocument JSON (config.json active_resume or an explicit path) and a list of CandidateEvidence records.
If missing: STOP and name the upstream skill — no resume JSON → run parse-resume; no evidence → run extract-evidence.

Purpose

Cross-reference a ResumeDocument against a list of CandidateEvidence records and produce a TruthReport that identifies which resume claims are supported, unsupported, or contradicted by evidence.

When to use

Before running update-keywords or update-terminology to ensure only truthful content is present.
After alignment to verify the aligned resume does not contain fabricated claims.
When the user wants an evidence-backed audit of a resume.

Inputs

Field	Type	Notes
`resume`	`ResumeDocument`	The resume to validate
`evidence`	`list[CandidateEvidence]`	Evidence records (may be empty; empty list produces a report with all claims unsupported)

Options (CapabilityOptions)

Option	Default	Effect
`strict`	false	Escalate advisory warnings to failures

no_llm has no effect — this capability is always deterministic.

How to invoke

CLI

resume-tool validate-truth --resume <resume.json> \
    [--evidence <evidence.json>] \
    [--output {json,text,md}] [--strict]

Read the full file on GitHub · 84 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.

4d ago First seen · 84 lines · 32 tokens per session scan A 26e58ecf2bce

Subscribe to this mod's changes

validate-facts is a skill published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 24d ago), licensed Apache-2.0. It adds 32 tokens to every session and 756 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-31.

Writing and docs

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