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.
npx skills add ai-analyst-lab/ai-analyst --skill experimentgit clone --depth 1 https://github.com/ai-analyst-lab/ai-analystWrote 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.
[](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/experiment)<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.
<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>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.
| Model | Per session | Once 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 |
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- experiment — 86% identical, 32 lines differ
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:
- Run Experiment Brief skill to capture hypothesis, north star, guardrails
- Invoke Experiment Designer agent
- Output:
experiments/{slug}/experiment.yaml(fromtemplates/experiment.yaml) Checkpoint: Config review (Type B — skippable with --just-do-it)
/experiment power
Purpose: Power analysis + duration estimation. Flow:
- Read
experiments/{slug}/experiment.yamlfor metric type, baseline, MDE - Call
helpers/stats/experiment_stats/power.py:- Proportion metric →
power_proportion(baseline_rate, mde) - Continuous metric →
power_mean(baseline_mean, baseline_std, mde)
- Proportion metric →
- Call
duration_estimate(total_sample, daily_traffic, allocation) - Update
experiment.yamlwith computed values (sample_size, duration, viable) - If NOT_VIABLE → suggest
/causal selectas 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:
- Read
experiments/{slug}/experiment.yamlfor pre-registered config - 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 - 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) - Effect size:
cohens_d(control, treatment) - Multiple comparisons:
adjust_pvalues(all_p_values, method="holm") - Guardrail checks against thresholds from experiment.yaml
- Segment analysis (Simpson's paradox check)
- Output:
experiments/{slug}/working/analysis_results.jsonCheckpoint: SRM gate (Type C — BLOCK halts everything)
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.
- 2d ago First seen · 173 lines · 89 tokens per session scan A 4eeb325633fa
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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.
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…