experiment

experiment is a skill for Claude Code from ai-analyst-lab/ai-analyst. It costs 89 tokens per session (1,950 once invoked), scanned A, original, MIT.

An experiment workflow for designing, sizing, analysing, interpreting, reporting, and monitoring controlled tests such as A/B tests, where one group receives a change and another acts as a comparison.

In plain words
What is it for?
Use it to define a test, estimate sample size and duration, measure treatment versus control, assess statistical evidence, and make a ship-or-no-ship decision.
Why use it?
It brings the steps of an experiment together and supports decisions about whether a change should be shipped. It also checks whether the test had enough data to detect a meaningful effect.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to define a test, estimate sample size and duration, measure treatment versus control, assess statistical evidence, and make a ship-or-no-ship decision.

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

Made for: Claude Code.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/experiment"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/experiment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,950 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.00089 $0.01950
Opus 5 $0.00044 $0.00975
Sonnet 5 $0.00018 $0.00390
Haiku 4.5 $0.00009 $0.00195

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

Security

Grade A, and why

experiment 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/experiment/SKILL.md · 173 lines

How it starts

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

Skill: /experiment — OpenXP Experimentation Platform

Purpose

Multi-mode skill for the full experiment lifecycle — from design through analysis to ship/no-ship decision. Orchestrates experiment agents and calls coded statistical helpers from helpers/stats/experiment_stats/ instead of improvising Python.

When to Use

Invoke as /experiment [mode] or trigger on experiment-related intents:

  • "I want to run an experiment"
  • "Analyze this A/B test"
  • "Did this experiment work?"
  • "What's the power for this test?"

Modes

/experiment design

Purpose: Create a pre-registered experiment config. Agent: agents/experiments/experiment-designer.md Flow:

  1. Run Experiment Brief skill to capture hypothesis, north star, guardrails
  2. Invoke Experiment Designer agent
  3. Output: experiments/{slug}/experiment.yaml (from templates/experiment.yaml) Checkpoint: Config review (Type B — skippable with --just-do-it)

/experiment power

Purpose: Power analysis + duration estimation. Flow:

  1. Read experiments/{slug}/experiment.yaml for metric type, baseline, MDE
  2. Call helpers/stats/experiment_stats/power.py:
    • Proportion metric → power_proportion(baseline_rate, mde)
    • Continuous metric → power_mean(baseline_mean, baseline_std, mde)
  3. Call duration_estimate(total_sample, daily_traffic, allocation)
  4. Update experiment.yaml with computed values (sample_size, duration, viable)
  5. If NOT_VIABLE → suggest /causal select as alternative Checkpoint: Power viability (Type C — NOT_VIABLE fires mandatory checkpoint)

/experiment analyze

Purpose: Run statistical tests on experiment data. Agent: agents/experiments/experiment-analyzer.md Flow:

  1. Read experiments/{slug}/experiment.yaml for pre-registered config
  2. SRM Gate (mandatory first step):
    from helpers.stats.experiment_stats import srm_check
    # Positional lists ONLY — do not pass dicts.
    # First arg: observed counts per variant (order must match expected_ratios).
    # Second arg: expected allocation ratios, summing to 1.0.
    result = srm_check([4218, 4196], [0.5, 0.5])
    # result = {"chi2_stat": 0.058, "p_value": 0.81, "verdict": "PASS", ...}
    if result["verdict"] == "BLOCK":
        # HALT — do not proceed to treatment effect analysis
    
  3. Treatment effect analysis using coded helpers:
    from helpers.stats.experiment_stats import welch_test, proportion_test, ratio_metric_test
    # Select based on metric type from experiment.yaml
    if metric_type == "proportion":
        result = proportion_test(c_success, c_n, t_success, t_n)
    elif metric_type == "continuous":
        result = welch_test(control_values, treatment_values)
    elif metric_type == "ratio":
        result = ratio_metric_test(num_c, den_c, num_t, den_t)
    
  4. Effect size: cohens_d(control, treatment)
  5. Multiple comparisons: adjust_pvalues(all_p_values, method="holm")
  6. Guardrail checks against thresholds from experiment.yaml
  7. Segment analysis (Simpson's paradox check)
  8. Output: experiments/{slug}/working/analysis_results.json Checkpoint: SRM gate (Type C — BLOCK halts everything)

Read the full file on GitHub · 173 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. 2d ago First seen · 173 lines · 89 tokens per session scan A 4eeb325633fa

Subscribe to this mod's changes

experiment is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (298 stars, last pushed 3d ago), licensed MIT. It adds 89 tokens to every session and 1,950 once invoked, about $0.0004 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-09-12.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens