experiment-design

experiment-design is a skill for Codex from uchicago-dsi/ai-sci-skills. It costs 43 tokens per session (622 once invoked), scanned A, original, MIT.

A workflow for designing the smallest experiment that can distinguish between important explanations and change a decision.

In plain words
What is it for?
Use it to plan experiments, ablations, benchmarks, debugging runs, and research or engineering test matrices with controls, predictions, readouts, and stop rules.
Why use it?
It prevents wasted runs and broad parameter sweeps that produce data without clarifying what to do next.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to plan experiments, ablations, benchmarks, debugging runs, and research or engineering test matrices with controls, predictions, readouts, and stop rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uchicago-dsi/ai-sci-skills/experiment-design
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 uchicago-dsi/ai-sci-skills --skill experiment-design
Clone the repo
git clone --depth 1 https://github.com/uchicago-dsi/ai-sci-skills

Made for: 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 experiment-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/uchicago-dsi/ai-sci-skills/experiment-design/github.svg)](https://agentmods.dev/skills/uchicago-dsi/ai-sci-skills/experiment-design)
Your own site
<a href="https://agentmods.dev/skills/uchicago-dsi/ai-sci-skills/experiment-design"><img src="https://agentmods.dev/badge/skills/uchicago-dsi/ai-sci-skills/experiment-design/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 experiment-design

Your own site · 80×15
<a href="https://agentmods.dev/skills/uchicago-dsi/ai-sci-skills/experiment-design"><img src="https://agentmods.dev/badge/skills/uchicago-dsi/ai-sci-skills/experiment-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 622 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.00043 $0.00622
Opus 5 $0.00022 $0.00311
Sonnet 5 $0.00009 $0.00124
Haiku 4.5 $0.00004 $0.00062

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

Security

Grade A, and why

experiment-design 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 10d 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/experiment-design/SKILL.md · 70 lines

How it starts

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

Experiment Design

Design For Decisions

  • The purpose of an experiment is to change a decision, not to accumulate runs.
  • Start from the decision that needs to be made.
  • Work backward to the smallest experiment that can separate the live hypotheses.

Use This Output Contract

When proposing an experiment, report:

  1. Decision to make.
  2. Live hypotheses.
  3. Nearest control or baseline.
  4. Minimal experiment matrix.
  5. Predicted outcomes by hypothesis.
  6. Readouts that will decide the result.
  7. Stop rule and follow-up rule.
  8. Baseline inheritance: what remains active if the candidate fails, and what evidence would be required to supersede it.

Apply These Rules

  • Every arm should exist for a reason.
  • If two arms would not change the decision differently, remove one.
  • Prefer one-variable changes over broad combinatorial sweeps.
  • Freeze everything not under test.
  • Use the nearest baseline, not a weak or outdated one.
  • If the baseline is unfair, stale, or confounded, fix that before treating the experiment as decision-worthy.
  • Prefer cheap discriminative checks before expensive cluster-scale runs.
  • Keep the best valid baseline as an explicit arm or immutable comparison until a prospectively defined successor beats it on the same decision readouts.
  • For every candidate, identify the exact delta from the baseline and what remains active if that delta fails.
  • Make stop rules hypothesis-scoped. Failure of an additive rescue or broader variant retires that addition or combination, not an unchanged successful parent method.

Choose Readouts Carefully

  • Pick the smallest set of metrics, artifacts, or visual checks that can separate the hypotheses.
  • Include a visual readout when failure modes are easier to see than summarize, for example overlays, curves, slices, masks, diff images, or before/after artifact views.
  • Include at least one readout that reflects the real success criterion, not just a proxy.
  • Name in advance what outcomes would favor each hypothesis.
  • Decide how you will interpret mixed results before launching.

Read the full file on GitHub · 70 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. 10d ago First seen · 70 lines · 43 tokens per session scan A ee76773a102b

Subscribe to this mod's changes

experiment-design is a skill published in the GitHub repository uchicago-dsi/ai-sci-skills (17 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 622 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

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

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

matlab

Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.

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

phylogenetics

Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.

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

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 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