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 skills/adityawrk/analytics-with-claude-code/ab-testnpx skills add adityawrk/analytics-with-claude-code --skill ab-testgit clone --depth 1 https://github.com/adityawrk/analytics-with-claude-codeWrote 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/adityawrk/analytics-with-claude-code/ab-test)<a href="https://agentmods.dev/skills/adityawrk/analytics-with-claude-code/ab-test"><img src="https://agentmods.dev/badge/skills/adityawrk/analytics-with-claude-code/ab-test.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.1 | $0.00059 | $0.04926 |
| Opus 5 | $0.00030 | $0.02463 |
| Sonnet 5 | $0.00012 | $0.00985 |
| Haiku 4.5 | $0.00006 | $0.00493 |
Grade A, and why
ab-test 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.
How it starts
The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A/B Test Analyzer
You are a senior experimentation analyst. When given A/B test data, you will perform a rigorous, multi-step analysis and produce a clear recommendation. Follow every step below. Do not skip steps. If data for a step is unavailable, note it as "Not Assessed" and explain what data would be needed.
Step 0: Environment Setup
import pandas as pd
import numpy as np
from scipy import stats
from scipy.stats import norm, chi2_contingency
import matplotlib
matplotlib.use('Agg')
import matplotlib.pyplot as plt
import warnings
warnings.filterwarnings('ignore')
SIGNIFICANCE_LEVEL = 0.05 # default, user can override
POWER = 0.80 # default, user can override
Step 1: Test Configuration Review
Before analyzing results, document the test setup:
TEST CONFIGURATION
==================
Test Name: [name]
Hypothesis: [clear statement: "Changing X will increase Y by Z%"]
Primary Metric: [e.g., conversion rate, revenue per user]
Secondary Metrics: [list]
Guardrail Metrics: [metrics that must NOT degrade, e.g., page load time, error rate]
Test Type: [A/B, A/B/C, A/B/n]
Allocation: [e.g., 50/50, 80/20]
Unit of Randomization: [user, session, device, cookie]
Start Date: [date]
End Date: [date or "still running"]
Target Population: [all users, mobile only, new users, etc.]
Minimum Detectable Effect (MDE): [X% relative change]
If the user does not provide these details, ask for them. The hypothesis and primary metric are essential -- do not proceed without them.
Step 2: Pre-Analysis Validation
2.1 Sample Ratio Mismatch (SRM) Test
This is the single most important diagnostic. If the actual split differs significantly from the expected split, the test is invalid.
def check_srm(n_control, n_treatment, expected_ratio=0.5):
"""
Chi-squared test for Sample Ratio Mismatch.
expected_ratio is the expected proportion in treatment.
"""
total = n_control + n_treatment
expected_control = total * (1 - expected_ratio)
expected_treatment = total * expected_ratio
chi2 = ((n_control - expected_control)**2 / expected_control +
(n_treatment - expected_treatment)**2 / expected_treatment)
p_value = 1 - stats.chi2.cdf(chi2, df=1)
actual_ratio = n_treatment / total
return {
'expected_ratio': expected_ratio,
'actual_ratio': round(actual_ratio, 4),
'chi2_statistic': round(chi2, 4),
'p_value': round(p_value, 6),
'srm_detected': p_value < 0.001, # use stricter threshold for SRM
'severity': 'CRITICAL' if p_value < 0.001 else 'OK'
}
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 · 500 lines · 59 tokens per session scan A 341308711c58
ab-test is a skill published in the GitHub repository adityawrk/analytics-with-claude-code (5 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 4,926 once invoked, about $0.0003 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-31.
Other skills, from other repositories
pr-verify
Verify a Docglow change actually works before submitting or merging a PR. Runs the conformance suite, then a behavioral verification pass (flag matrix, artifact-join spot checks, pipeline contract sweep, payload budget). Use when reviewing a PR, self-reviewing a branch before opening a PR, or when asked to "verify…
developing-incremental-models
Develops and troubleshoots dbt incremental models. Use when working with incremental materialization for: (1) Creating new incremental models (choosing strategy, uniquekey, partition) (2) Task mentions "incremental", "append", "merge", "upsert", or "late arriving data" (3) Troubleshooting incremental failures (merge…
altimate-code
Delegates dbt and warehouse work to altimate-code, a specialized CLI agent with 100+ purpose-built data tools. USE THIS SKILL FIRST whenever the task mentions or implies: warehouse access (Snowflake, BigQuery, Redshift, Databricks, Postgres, MySQL, DuckDB), column-level lineage, downstream-impact analysis, dbt builds…
debugging-dbt-errors
Debugs and fixes dbt errors systematically. Use when working with dbt errors for: (1) Task mentions "fix", "error", "broken", "failing", "debug", "wrong", or "not working" (2) Compilation Error, Database Error, or test failures occur (3) Model produces incorrect output or unexpected results (4) Need to troubleshoot…
documenting-dbt-models
Documents dbt models and columns in schema.yml. Use when working with dbt documentation for: (1) Adding model descriptions or column definitions to schema.yml (2) Task mentions "document", "describe", "description", "dbt docs", or "schema.yml" (3) Explaining business context, grain, meaning of data, or business rules…
refactoring-dbt-models
Safely refactors dbt models with downstream impact analysis. Use when restructuring dbt models for: (1) Task mentions "refactor", "restructure", "extract", "split", "break into", or "reorganize" (2) Extracting CTEs to intermediate models or creating macros (3) Modifying model logic that has downstream consumers (4)…