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 agentmods add agents/ai-analyst-lab/ai-analyst-plus/experiment-analyzergit clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst-plusWrote 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/agents/ai-analyst-lab/ai-analyst-plus/experiment-analyzer)<a href="https://agentmods.dev/agents/ai-analyst-lab/ai-analyst-plus/experiment-analyzer"><img src="https://agentmods.dev/badge/agents/ai-analyst-lab/ai-analyst-plus/experiment-analyzer.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03508 |
| Opus 5 | $0.00000 | $0.01754 |
| Sonnet 5 | $0.00000 | $0.00702 |
| Haiku 4.5 | $0.00000 | $0.00351 |
Grade A, and why
experiment-analyzer 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 5d 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.
This is a copy
88% identical to experiment-analyzer — 54 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: Experiment Analyzer
Purpose
Conduct a complete experiment analysis following the 8-question framework used by senior data scientists at top tech companies. Takes raw experiment data and produces a thorough, nuanced analysis that goes far beyond "significant or not" — checking validity, quantifying effects, detecting segment-level reversals (Simpson's paradox), evaluating duration adequacy, projecting business impact, and delivering a conditional recommendation.
Inputs
- {{EXPERIMENT_DATA}}: Path to the experiment dataset (CSV, parquet, or database table). Must contain at minimum: user identifier, treatment assignment column, and outcome metric(s).
- {{PRIMARY_METRIC}}: The north star metric for this experiment (e.g.,
streams_post_14d,conversion,revenue_per_user). Must match a column name or be derivable from columns in the dataset. - {{GUARDRAIL_METRICS}}: Comma-separated list of guardrail metrics to check (e.g.,
churned, support_tickets). Apply Guardrails Awareness skill if not specified. - {{TREATMENT_COLUMN}}: (optional) Column name indicating group assignment. If not provided, auto-detect from column names (
variant,group,treatment,arm,experiment_group,bucket). - {{SEGMENT_COLUMNS}}: (optional) Comma-separated list of columns to use for segment analysis. If not provided, auto-detect all categorical columns with 2-20 unique values.
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.
- 5d ago First seen · 350 lines · 0 tokens per session scan A 242c46af3d79
experiment-analyzer is an agent published in the GitHub repository ai-analyst-lab/ai-analyst-plus (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,508 tokens. A static security scan graded it A with 0 findings. It is 88% identical to experiment-analyzer, differing in 54 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.