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.
npx skills add pandysp/claude-plugins --skill verify-claimsgit clone --depth 1 https://github.com/pandysp/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/pandysp/claude-plugins/verify-claims)<a href="https://agentmods.dev/skills/pandysp/claude-plugins/verify-claims"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/verify-claims/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.
<a href="https://agentmods.dev/skills/pandysp/claude-plugins/verify-claims"><img src="https://agentmods.dev/badge/skills/pandysp/claude-plugins/verify-claims.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00131 | $0.00775 |
| Opus 5.5 | $0.00052 | $0.00310 |
| Sonnet 5.5 | $0.00026 | $0.00155 |
| Haiku 4.5 | $0.00013 | $0.00077 |
Grade A, and why
verify-claims 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify claims: find the proof or say you can't
You construct narratives (plausible stories assembled from pattern-matching) and present them as conclusions. Sometimes confidently, sometimes hedged with "likely" or "probably." Either way, the user can't distinguish your verified knowledge from your confabulations without doing the verification work themselves. This skill forces that work onto you, where it belongs.
1. Identify claims
Scan your most recent substantive response for factual assertions:
- Causal: "X caused Y", "this broke because…"
- State: "the system does X", "the field contains Y", "the config is set to Z"
- Historical: "this worked before", "it changed between A and B"
- Attribution: "someone edited this", "the platform updated their policy"
- Hedged: anything with "likely", "probably", "presumably", "appears to", "seems like", "suggests that." Hedging is the marker that you know you're uncertain but are stating the claim anyway.
2. Extract unverified claims
For each claim, ask: what is my proof for this specific claim? If the answer is any of these, the claim is unverified:
- "My training data"
- "It's the most plausible explanation"
- "It's how these things usually work"
- "I inferred it from context"
- Nothing
List each unverified claim with: the exact text, what proof is missing, and whether it was stated confidently or hedged.
3. Plan verification
Pick the right method per claim type:
| Claim type | Verification method |
|---|---|
| Platform/API behavior | Changelogs, docs, community posts |
| Current code/system state | Read the code, grep the codebase |
| Historical state | git log, git blame, execution logs |
| Causal ("X caused Y") | Need proof for both: X happened AND Y follows from X |
| Quantitative | Run the measurement |
| External fact | Authoritative sources, expert communities |
4. Execute and classify
Run each verification. Classify the result:
- VERIFIED: definitive proof found. Cite it.
- PARTIAL: some parts proven, others aren't. State exactly which.
- INCONCLUSIVE: searched, found nothing either way. State what you searched. Do not restate the claim as a conclusion.
- DISPROVEN: found contradicting proof. Correct the record.
- UNVERIFIABLE: no feasible way to check. Explain why.
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.
- 1mo ago First seen · 61 lines · 131 tokens per session scan A 86fcfb37eb29
verify-claims is a skill published in the GitHub repository pandysp/claude-plugins (6 stars, last pushed 7d ago), licensed MIT. It adds 131 tokens to every session and 775 once invoked, about $0.0005 per session on Opus 5.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.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
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…
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…