claim-source-verification

claim-source-verification is a skill for Claude Code, Codex from Boom5426/Nature-Paper-Skills. It costs 82 tokens per session (2,597 once invoked), scanned A, original, MIT.

A process for checking whether cited sources actually support the claims made in a manuscript. It checks the connection between each claim and its evidence, not just whether a paper exists or has correct citation details.

In plain words
What is it for?
Use it to review proposed references, verify literature-search results, audit claim-to-source matches, and reject citations that do not substantiate the text.
Why use it?
A real, correctly formatted paper can still be the wrong source for a sentence. This process catches unsupported conclusions, incorrect metadata, mismatched populations or sites, and sources that are not primary when one is required.

Skill for Claude CodeCodex

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

Good fit Use it to review proposed references, verify literature-search results, audit claim-to-source matches, and reject citations that do not substantiate the text.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/boom5426/nature-paper-skills/claim-source-verification
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 Boom5426/Nature-Paper-Skills --skill claim-source-verification
Clone the repo
git clone --depth 1 https://github.com/Boom5426/Nature-Paper-Skills

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 claim-source-verification

README.md
[![agentmods](https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/claim-source-verification/github.svg)](https://agentmods.dev/skills/boom5426/nature-paper-skills/claim-source-verification)
Your own site
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/claim-source-verification"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/claim-source-verification/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 claim-source-verification

Your own site · 80×15
<a href="https://agentmods.dev/skills/boom5426/nature-paper-skills/claim-source-verification"><img src="https://agentmods.dev/badge/skills/boom5426/nature-paper-skills/claim-source-verification.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 82 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,597 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 76
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00082 $0.02597
Opus 5 $0.00041 $0.01299
Sonnet 5 $0.00016 $0.00519
Haiku 4.5 $0.00008 $0.00260

Measured 12d ago against content hash 0d594cb6dd5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

claim-source-verification 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 12d 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/core/claim-source-verification/SKILL.md · 230 lines

How it starts

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

Claim-Source Verification

Overview

A citation can be perfectly real, perfectly formatted, and still wrong, because the paper it points to does not say what the sentence claims it says. That is the failure this skill exists to catch, and it is the dominant one.

The calibration comes from a real Review manuscript. Seven research agents proposed 139 sources to resolve 44 open factual questions. An independent skeptic then re-checked every one. It rejected 55.

Rejection class Count
does_not_support_claim 29
metadata_wrong 12
wrong_site_or_population 6
not_primary_but_required_to_be 5
paywalled_unverifiable 3

None was fabricated. Every rejected source was a real, findable paper with a real DOI. An existence check would have passed all 139. A metadata check would have caught 12. The largest class, more than half of all rejections, is invisible to both: a genuine paper made to carry a conclusion it does not reach.

So the operating rule is: a source's existence is not evidence that it supports the claim, and a clean bibliography audit is not evidence of anything at all.

When To Use

Use this skill when:

  • an agent, a collaborator, or a literature-search tool has proposed references and nothing has adversarially checked them yet
  • a manuscript makes quantitative claims (limits, thresholds, error rates, standard clauses, benchmark numbers) that trace to cited sources
  • open factual or sourcing markers are being closed out in batch
  • a Review or survey is being sourced, where most claims are about other people's measurements rather than the author's own

Do not use this skill for:

  • duplicate BibTeX keys, DOI syntax, missing fields, placeholder entries. That is citation-verifier, and it runs before this, not instead of it.
  • discovering literature from scratch. That is academic-researcher, installed with --set all. This skill checks what such a pass produces.
  • deciding whether a claim is interesting. That is manuscript-optimizer.

Read the full file on GitHub · 230 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 230 lines · 82 tokens per session scan A 0d594cb6dd5e

Subscribe to this mod's changes

claim-source-verification is a skill published in the GitHub repository Boom5426/Nature-Paper-Skills (490 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 2,597 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-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