claims-audit

claims-audit is a skill for Claude Code from jeonnoin-alt/Eureka. It costs 34 tokens per session (4,332 once invoked), scanned A, original, MIT.

A manuscript-auditing workflow that checks whether numerical claims, figures, and reported results are supported by actual files and reproducible scripts.

In plain words
What is it for?
Use it during or after manuscript writing to trace every number to a source file, check figure generation, and review whether results are reported completely.
Why use it?
It catches unsupported numbers, missing negative results, and figures whose origin or integrity cannot be verified before publication.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the Eureka plugin — 16 skills, 1 agent, 1 hook shipped together

Good fit Use it during or after manuscript writing to trace every number to a source file, check figure generation, and review whether results are reported completely.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jeonnoin-alt/eureka/claims-audit
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 jeonnoin-alt/Eureka --skill claims-audit
Clone the repo
git clone --depth 1 https://github.com/jeonnoin-alt/Eureka

Made for: Claude Code.

Or install Eureka, the plugin that ships this one along with the rest of its 16 skills, 1 agent, 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.

agentmods badge for claims-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/claims-audit/github.svg)](https://agentmods.dev/skills/jeonnoin-alt/eureka/claims-audit)
Your own site
<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/claims-audit"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/claims-audit/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 claims-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/claims-audit"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/claims-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,332 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.
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.00034 $0.04332
Opus 5 $0.00017 $0.02166
Sonnet 5 $0.00007 $0.00866
Haiku 4.5 $0.00003 $0.00433

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

Security

Grade A, and why

claims-audit 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 11d 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/claims-audit/SKILL.md · 413 lines

How it starts

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

Claims Audit

Verify that every number, every figure, and every reported experiment in a manuscript is traceable, reproducible, and complete. This skill subsumes negative-results reporting and figure integrity into a unified audit.

The Iron Law:

EVERY NUMBER IN THE MANUSCRIPT MUST TRACE TO A SPECIFIC FILE. NO EXCEPTIONS.

A number without a source file is not a finding — it is an assertion. Assertions do not belong in scientific papers.

When to Use

Use this skill:

  • After any manuscript draft is produced
  • Before submitting to any journal
  • Before any internal review round
  • When verification-before-publication requests a claims audit
  • When a coauthor asks "where does this number come from?"

Do NOT use this skill to:

  • Run experiments (use experiment-design)
  • Generate figures (use the analysis/visualization scripts)
  • Write manuscript sections (use the manuscript-writer agent)

Announce at Start

At the beginning of every session using this skill, state:

"I'm running the claims-audit skill. This will audit number traceability, figure integrity, and completeness of reported results."


The Three Audit Components

Component A: Number Traceability

For every quantitative claim in the manuscript — correlation coefficients, p-values, sample sizes, percentages, improvement margins, AUC values, effect sizes, anything with a number — the claim must be traceable to a specific file and a specific line or cell that produced it.

Process:

  1. Extract every quantitative claim from the manuscript. Work section by section: Abstract, Introduction (any quantitative statements), Methods (N, parameters), Results (all reported statistics), Discussion (any numbers not already extracted).
  2. For each claim, identify the source file in results/ (or equivalent output directory).
  3. Find the exact line, JSON key, CSV row, or notebook cell that produces that number.
  4. Compare the manuscript value to the source value character by character. Rounding is acceptable only if it is the correct rounding of the source value — verify this explicitly.
  5. Flag any discrepancy as CRITICAL.

Read the full file on GitHub · 413 lines

Files

What ships with it

1 file 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. 11d ago First seen · 413 lines · 34 tokens per session scan A 50abd15cee59

Subscribe to this mod's changes

claims-audit is a skill published in the GitHub repository jeonnoin-alt/Eureka (2 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 4,332 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.

Related

Other skills, from other repositories

binder-design-campaign

Gated protein design campaign: each expert judgement is a checkpoint a human signs off before compute is spent. Branches: de novo binder design (epitope choice, generation, co-folding ensemble ranking, ranked order sheet); structure and complex prediction with calibrated confidence; protein engineering (stability…

SPYfighting/my-academic-skills · 148 tokens

scientific-illustrator-local

Rebuild scientific schematic images as editable SVG and Adobe Illustrator paths with live text, or draw new scientific diagrams from explicit content. Use for raster-to-vector reconstruction, editable paper figures, and local Illustrator drawing. Separates labels from tracing and preserves existing artwork through a…

SPYfighting/my-academic-skills · 82 tokens

training-plan

Create personalized training plans for 5K, 10K, Half Marathon, and Marathon races. Use when the user requests a training plan for any of these distances, wants to prepare for a race, or asks for a structured running program. This skill generates comprehensive markdown training plans that include race goals, training…

ColinEberhardt/claude-running-coach · 78 tokens

class-generation

Generate openEHR class documentation — class-definition tables, effective views, and UML class/package diagrams — from BMM schemas with the bmm-publisher tool, for specifications-XX repos and their docs/UML/ content. This skill should be used when the user asks to regenerate class tables, run bmm-publisher, generate…

openEHR/ai-plugins · 124 tokens

scientific-figure-prompt-compiler

Transform concise scientific or technical descriptions into structured visual specifications and high-quality image-generation prompts. Use for scientific figures, technical diagrams, system architectures, mechanisms, workflows, spatial models, timelines, layered systems, and information-dense visuals. Model-agnostic…

basejb/skills · 72 tokens

onekgpd

Query the 1000 Genomes Project dataset (3,202 whole-genome-sequenced individuals, GRCh38) at the level of individual participants. Use when a question is about individuals or variants in the 1000 Genomes Project cohort: which individuals carry variants matching specific criteria in a gene or region, which individuals…

K-Dense-AI/scientific-agent-skills · 143 tokens