experiment-analysis

experiment-analysis is a skill for Claude Code, Codex from uthumany/uthy-legacy-os. It costs 29 tokens per session (758 once invoked), scanned A, original, MIT.

A guide for analyzing completed experiments, including A/B tests where two versions are compared. It checks whether the data is trustworthy, measures the size of the effect, and helps explain what happened.

In plain words
What is it for?
Use it after an experiment to decide whether to release the change, improve it, or stop it, and to investigate why the result occurred.
Why use it?
It helps you avoid decisions based on tests that ran too briefly, had tracking problems, uneven groups, or effects that disappeared over time.

Skill for Claude CodeCodex

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

Good fit Use it after an experiment to decide whether to release the change, improve it, or stop it, and to investigate why the result occurred.

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

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-analysis

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/experiment-analysis"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/experiment-analysis.svg" alt="Reviewed on agentmods" width="80" 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 758 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.00029 $0.00758
Opus 5.5 $0.00012 $0.00303
Sonnet 5.5 $0.00006 $0.00152
Haiku 4.5 $0.00003 $0.00076

Measured 2mo ago against content hash 6e14f087b463, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

experiment-analysis 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 2mo 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/measuring/experiment-analysis/SKILL.md · 82 lines

How it starts

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

Experiment Analysis

Overview

Running the experiment is only half the work — analyzing the results correctly is where the value lives. This skill helps you interpret experiment data, avoid common statistical pitfalls, and make confident go/kill decisions.

When to Use

  • An A/B test or experiment has concluded
  • You need to decide whether to ship, iterate, or kill
  • You want to understand not just the outcome but WHY it happened
  • Don't use for: pre-experiment planning (use experiment-design skill), exploratory data analysis (different approach)

Instructions

1. Check Experiment Validity

Before analyzing results, verify:

  • Sample size: Did you reach the required sample size?
  • Duration: Did the experiment run long enough? (minimum 1 full business cycle, usually 1-2 weeks)
  • Novelty effect: Did the effect change over time? (compare first few days vs. last few days)
  • Sample ratio mismatch: Are the control/treatment group sizes as expected?
  • Data quality: Any tracking issues, bugs, or outliers?

2. Read the Primary Metric

  • Statistical significance: p-value < 0.05 (or your pre-defined threshold)
  • Effect size: How big is the impact? (absolute and relative)
  • Confidence interval: What's the range of plausible effects?
  • Practical significance: Even if statistically significant, is this effect worth building?

3. Analyze Guardrail Metrics

What metrics should NOT have degraded?

  • Check ALL guardrail metrics for statistically significant negative changes
  • A negative guardrail doesn't automatically kill the experiment, but it requires discussion
  • Trade-off decision: Is the primary lift worth the guardrail degradation?

4. Segment Analysis

  • Break down results by key segments (new vs. existing users, platform, plan type)
  • A negative overall result might hide a strong positive in a specific segment
  • Be cautious of over-segmenting (too many slices = false positives)

5. Qualitative Signals

  • What did user feedback say during the experiment?
  • Any support tickets related to the change?
  • Any unexpected user behavior observed?

Read the full file on GitHub · 82 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. 2mo ago First seen · 82 lines · 29 tokens per session scan A 6e14f087b463

Subscribe to this mod's changes

experiment-analysis is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 758 once invoked, about $0.0001 per session on Opus 5.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

experiment-analysis compared with skills from other repositories

experiment-analysis next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
experiment-analysisuthumany/uthy-legacy-osSkill55mo agoMITA29Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex