exp-eval

exp-eval is a skill for Claude Code, Codex from skyllwt/AutoSci. It costs 29 tokens per session (3,539 once invoked), scanned A, original, MIT.

An experiment-review command that judges completed experiment results against a linked idea’s hypothesis and records the outcome in a research wiki.

In plain words
What is it for?
Use it to mark an idea as supported, partly supported, unsupported, or inconclusive, update its failure details and relationships, and rebuild the wiki’s research summaries.
Why use it?
It turns experimental evidence into a clear decision instead of leaving results disconnected from the idea they were meant to test.

Skill for Claude CodeCodex

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/skyllwt/autosci/exp-eval
Any agent
npx skills add skyllwt/AutoSci --skill exp-eval
Clone the repo
git clone --depth 1 https://github.com/skyllwt/AutoSci

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 exp-eval

README.md
[![agentmods](https://agentmods.dev/badge/skills/skyllwt/autosci/exp-eval.svg)](https://agentmods.dev/skills/skyllwt/autosci/exp-eval)
Your own site
<a href="https://agentmods.dev/skills/skyllwt/autosci/exp-eval"><img src="https://agentmods.dev/badge/skills/skyllwt/autosci/exp-eval.svg" alt="Measured on agentmods" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,539 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.

ModelPer sessionOnce invoked
Fable 5 $0.00029 $0.03539
Opus 5 $0.00015 $0.01769
Sonnet 5 $0.00006 $0.00708
Haiku 4.5 $0.00003 $0.00354

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

Security

Grade A, and why

exp-eval 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.

.claude/skills/exp-eval/SKILL.md · 321 lines

How it starts

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

/exp-eval

Convert completed experiment results into wiki knowledge updates. Review LLM acts as an impartial judge (following cross-model-review), independently evaluating how experimental results affect the linked idea's hypothesis. Four verdict paths: supported → idea validated / partially_supported → supplementary experiments / not_supported → idea failed / inconclusive → debug. Auto-updates the linked idea's status, failure_reason, and graph edges.

Inputs

  • experiment: slug from wiki/experiments/ (status must be completed)
  • --auto (optional): automatic mode — do not pause for user confirmation before wiki updates (used when called by /research)

Outputs

  • wiki/ideas/{linked-idea}.md — updated status, failure_reason, date_resolved
  • wiki/experiments/{slug}.md## Idea updates section filled in (records the linked idea's status transition; replaces the legacy ## Claim updates heading)
  • wiki/graph/edges.jsonl — new supports / invalidates edges added (experiment → idea)
  • wiki/graph/context_brief.md — rebuilt
  • wiki/graph/open_questions.md — rebuilt
  • wiki/log.md — appended log entry
  • VERDICT_REPORT (printed to terminal) — verdict result, wiki change summary, next step suggestions

Wiki Interaction

Reads

  • wiki/experiments/{slug}.md — experiment results: outcome, key_result, metrics, full Results section, linked_idea
  • wiki/ideas/{linked-idea}.md — linked idea current state: status, ## Hypothesis, ## Risks
  • wiki/experiments/*.md — sibling experiments with the same linked_idea (aggregate assessment)
  • wiki/graph/context_brief.md — global context
  • .claude/skills/shared-references/cross-model-review.md — reviewer independence principle

Writes

  • wiki/ideas/{linked-idea}.md — update status, failure_reason, date_resolved
  • wiki/experiments/{slug}.md — fill in ## Idea updates section
  • wiki/graph/edges.jsonl — add supports / invalidates edges (experiment → idea)
  • wiki/graph/context_brief.md — rebuild
  • wiki/graph/open_questions.md — rebuild
  • wiki/log.md — append operation log

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

  1. 4d ago First seen · 321 lines · 29 tokens per session scan A 145fb5be1d67

Subscribe to this mod's changes

exp-eval is a skill published in the GitHub repository skyllwt/AutoSci (1,659 stars, last pushed 5d ago), licensed MIT. It adds 29 tokens to every session and 3,539 once invoked, about $0.0001 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

exploratory-data-analysis

Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

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

nature-statistics

Audit, revise, or draft manuscript statistical reporting for Nature / high-impact journal submissions. Use when the user asks to check statistical analysis sections, p values, confidence intervals, sample size, biological versus technical replicates, randomization, blinding, multiple-comparison correction, model…

Yuan1z0825/nature-skills · 139 tokens

evaluating-with-leakage-gates

Evaluate an OpenMed de-identification or clinical NER model against the leakage-first release gates G1a through G8, which gate releases on residual PHI leakage rather than on F1. Use when the user wants to run the OpenMed eval harness on a synthetic golden set, decide whether a de-id model is RELEASABLE or…

maziyarpanahi/openmed · 158 tokens

mapping-to-snomed

Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…

maziyarpanahi/openmed · 205 tokens

mixed-precision

Use FP16/BF16 mixed precision to accelerate training and reduce memory. Use when optimizing GPU performance.

aiming-lab/AutoResearchClaw · 25 tokens

indication-dossier

Build a source-backed biomedical indication dossier. Use when a research task asks for disease biology, target rationale, patient segmentation, biomarkers, trials, drugs, competitive landscape, or translational evidence.

companion-inc/feynman · 43 tokens