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 jeonnoin-alt/Eureka --skill verification-before-publicationgit clone --depth 1 https://github.com/jeonnoin-alt/EurekaWrote 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/jeonnoin-alt/eureka/verification-before-publication)<a href="https://agentmods.dev/skills/jeonnoin-alt/eureka/verification-before-publication"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/verification-before-publication/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/jeonnoin-alt/eureka/verification-before-publication"><img src="https://agentmods.dev/badge/skills/jeonnoin-alt/eureka/verification-before-publication.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.00030 | $0.02283 |
| Opus 5 | $0.00015 | $0.01141 |
| Sonnet 5 | $0.00006 | $0.00457 |
| Haiku 4.5 | $0.00003 | $0.00228 |
Grade A, and why
verification-before-publication 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.
How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Publication
Overview
Claiming results are publication-ready without verification is not confidence — it is a liability to your co-authors, your field, and your career.
Core principle: Evidence before submission, always.
Violating the letter of this rule is violating the spirit of this rule.
The Iron Law
NO SUBMISSION CLAIM WITHOUT FRESH VERIFICATION EVIDENCE
If you haven't re-run the verification in this session, you cannot claim it is ready for submission.
The Gate Function
BEFORE claiming publication-ready:
1. IDENTIFY: What evidence proves each claim?
2. RUN: Re-run key analyses fresh (not cached results)
3. READ: Full output, check every number
4. VERIFY: Does output match manuscript claims?
- If NO: State actual values with evidence
- If YES: State verification WITH evidence
5. ONLY THEN: Claim ready for submission
Skip any step = asserting, not verifying
Common Failures
| Claim | Requires | Not Sufficient |
|---|---|---|
| Results are accurate | claims-audit PASS | "I checked last week" |
| Figures are correct | Re-generated figures match manuscript | "They look right" |
| Analysis is reproducible | Single command reproduces all results | "It worked on my machine" |
| Statistics are proper | hypothesis-first INTERPRET standards met (effect size + CI + correction) | "p-values are significant" |
| All results reported | Experiment log cross-referenced with manuscript | "Main results are in" |
Red Flags — STOP
- Using "should be", "probably fine", "I'm confident"
- Expressing readiness before verification ("It's ready", "We're good to go", "Just needs a polish")
- About to submit or share without re-running analyses
- Relying on results from a previous session
- Trusting cached outputs without checking they match current code
- Thinking "just this once — deadline is today"
- Under pressure from collaborators or journal deadlines
- ANY wording implying submission-readiness without having run fresh verification
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.
- 11d ago First seen · 211 lines · 30 tokens per session scan A 3f3bec53b24f
verification-before-publication is a skill published in the GitHub repository jeonnoin-alt/Eureka (2 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 2,283 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.
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…
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…
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…
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…
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…
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…