experiment-design

experiment-design is a skill for Claude Code, Codex from leonardodalinky/SciDER. It costs 46 tokens per session (2,005 once invoked), scanned A, original, Apache-2.0.

A guide to planning controlled experiments so their results can be interpreted and repeated. It covers hypotheses, comparison baselines, sample sizes, confounding factors, and reproducibility.

In plain words
What is it for?
Use it to define research hypotheses, choose baselines and metrics, estimate sample sizes, control confounds, set random seeds, and report results responsibly.
Why use it?
It helps prevent experiments that are too small, unfairly compared, or changed after seeing the results. It also makes unexpected findings easier to check.

Skill for Claude CodeCodex

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

Good fit Use it to define research hypotheses, choose baselines and metrics, estimate sample sizes, control confounds, set random seeds, and report results responsibly.

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

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 experiment-design

README.md
[![agentmods](https://agentmods.dev/badge/skills/leonardodalinky/scider/experiment-design/github.svg)](https://agentmods.dev/skills/leonardodalinky/scider/experiment-design)
Your own site
<a href="https://agentmods.dev/skills/leonardodalinky/scider/experiment-design"><img src="https://agentmods.dev/badge/skills/leonardodalinky/scider/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/leonardodalinky/scider/experiment-design"><img src="https://agentmods.dev/badge/skills/leonardodalinky/scider/experiment-design.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,005 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.00046 $0.02005
Opus 5 $0.00023 $0.01002
Sonnet 5 $0.00009 $0.00401
Haiku 4.5 $0.00005 $0.00200

Measured 9d ago against content hash 95825e1d2d39, 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 9d 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.

.scider/skills/experiment-design/SKILL.md · 243 lines

How it starts

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

Experiment Design

Overview

Good experimental design determines whether your results are interpretable, valid, and reproducible. This skill covers the process from hypothesis formation through post-experiment reporting, with actionable checklists and code examples.

When to Use This Skill

  • Before designing any experiment: choose baselines, define metrics, plan sample sizes
  • When writing a research idea: include a concrete experimental protocol
  • When results look unexpected: check whether experimental design is the cause
  • When a reviewer asks about confounds, baselines, or statistical power

Hard Rules

  1. Define your hypothesis BEFORE collecting data — post-hoc hypothesis selection inflates false positive rates
  2. Always include at least one trivial baseline — random, majority class, or simple heuristic
  3. Set random seeds everywhere — numpy, random, torch, tensorflow, sklearn
  4. Use held-out test data only once — never tune on it
  5. Report N (sample size) and how it was determined — underpowered studies mislead

1. Hypothesis Formation

A well-formed hypothesis has three parts:

Part Example
Null hypothesis (H₀) The proposed method performs no better than the baseline
Alternative hypothesis (H₁) The proposed method achieves higher F1 than the baseline
Expected effect size Δ = 0.03 F1 (3 percentage points)

Directionality:

  • One-tailed: you predict direction of effect (method > baseline) → more statistical power, but only justified if direction is theoretically grounded
  • Two-tailed: you test for any difference → safer for exploratory work

2. Statistical Power and Sample Size

Power analysis determines how many samples you need to detect an effect of a given size.

Key parameters:

  • α (Type I error rate): probability of false positive — typically 0.05
  • β (Type II error rate): probability of false negative — typically 0.20
  • Power = 1 - β = 0.80 (minimum), 0.90 (preferred)
  • Effect size: domain-specific (Cohen's d for continuous, Cohen's h for proportions)

Read the full file on GitHub · 243 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. 9d ago First seen · 243 lines · 46 tokens per session scan A 95825e1d2d39

Subscribe to this mod's changes

experiment-design is a skill published in the GitHub repository leonardodalinky/SciDER (88 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 2,005 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-30.

Related

Other skills, from other repositories

paper-polish

Polishes existing academic prose while preserving the author's meaning: grammar and flow repair, tone calibration against evidence strength, AI-tone removal, and Chinese-to-English rewriting at submission quality. Never fabricates data, citations, or claims, and flags any edit that could change scientific meaning. Use…

HKUSTDial/Supervisor-Skills · 93 tokens

paper-writer

Drafts publishable paper prose from the author's own materials, from a single paragraph to a full manuscript, across STEM and non-STEM fields. Every factual claim traces to user input, verified retrieval, or field common knowledge; citations pass an independent verification ladder; delivery is clean prose with zero…

HKUSTDial/Supervisor-Skills · 90 tokens

pre-submission-reviewer

Runs a pre-submission review of a technical paper across five dimensions: macro logic, writing details, English grammar, LaTeX formatting, and figure quality. Uses a reviewer-style severity taxonomy (CRITICAL / MAJOR / MINOR) and flags banned AI-tone vocabulary and em-dash misuse. Use when the user asks to 'review…

HKUSTDial/Supervisor-Skills · 104 tokens

intro-drafter

Drafts the Introduction prose for a technical paper, guided internally by a six-paragraph flowchart: background and running example, existing limitations, problem essence and goal, key challenges, solution overview, contributions. Positions the paper as Technique or New Problem/Setting, aligns contributions with…

HKUSTDial/Supervisor-Skills · 95 tokens

figure-designer

Advises on the design of the three core figures in a technical paper: the Motivated Example (Figure 1), the Solution Overview (Methodology), and the Experimental Results figures. Recommends the right design paradigm, layout, labelling, and tool for each figure type, then runs a quality-control audit. Use when the user…

HKUSTDial/Supervisor-Skills · 112 tokens

tech-paper-template

Structures a technical paper's full logical skeleton using a thinking-template table (research background, limitations, key idea or goal, challenges, methodology modules, contributions), positions the paper as Technique or New Problem/Setting, and runs a four-point self-consistency check. Use when the user is…

HKUSTDial/Supervisor-Skills · 100 tokens