ab-testing

ab-testing is a skill for Claude Code, Codex from rondoflow/rondoflow. It costs 165 tokens per session (6,481 once invoked), scanned A, original, MIT.

An A/B testing guide for comparing two versions of a product change, such as different copy or layouts, with planned measurements.

In plain words
What is it for?
Use it to define a test hypothesis, choose what to measure, plan the sample size, and account for product context, constraints, and available tools.
Why use it?
It helps avoid guessing which version works better and reduces the risk of drawing conclusions from too little or poorly collected data.

Skill for Claude CodeCodex

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

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.

agentmods
npx agentmods add skills/rondoflow/rondoflow/ab-testing
Any agent
npx skills add rondoflow/rondoflow --skill ab-testing
Clone the repo
git clone --depth 1 https://github.com/rondoflow/rondoflow

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 ab-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/rondoflow/rondoflow/ab-testing.svg)](https://agentmods.dev/skills/rondoflow/rondoflow/ab-testing)
Your own site
<a href="https://agentmods.dev/skills/rondoflow/rondoflow/ab-testing"><img src="https://agentmods.dev/badge/skills/rondoflow/rondoflow/ab-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 165 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,481 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00165 $0.06481
Opus 5 $0.00082 $0.03240
Sonnet 5 $0.00033 $0.01296
Haiku 4.5 $0.00016 $0.00648

Measured 6d ago against content hash be0a2b4c65e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ab-testing 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 6d 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.

packages/catalog/content/skills/ab-testing/SKILL.md · 909 lines

How it starts

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

A/B Test Setup

You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results.

Initial Assessment

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a test, understand:

  1. Test Context - What are you trying to improve? What change are you considering?
  2. Current State - Baseline conversion rate? Current traffic volume?
  3. Constraints - Technical complexity? Timeline? Tools available?

Core Principles

1. Start with a Hypothesis

  • Not just "let's see what happens"
  • Specific prediction of outcome
  • Based on reasoning or data

2. Test One Thing

  • Single variable per test
  • Otherwise you don't know what worked

3. Statistical Rigor

  • Pre-determine sample size
  • Don't peek and stop early
  • Commit to the methodology

4. Measure What Matters

  • Primary metric tied to business value
  • Secondary metrics for context
  • Guardrail metrics to prevent harm

Hypothesis Framework

Structure

Because [observation/data],
we believe [change]
will cause [expected outcome]
for [audience].
We'll know this is true when [metrics].

Example

Weak: "Changing the button color might increase clicks."

Strong: "Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start."


Test Types

Type Description Traffic Needed
A/B Two versions, single change Moderate
A/B/n Multiple variants Higher
MVT Multiple changes in combinations Very high
Split URL Different URLs for variants Moderate

Read the full file on GitHub · 909 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 6d ago First seen · 909 lines · 165 tokens per session scan A be0a2b4c65e3

Subscribe to this mod's changes

ab-testing is a skill published in the GitHub repository rondoflow/rondoflow (20 stars, last pushed 2d ago), licensed MIT. It adds 165 tokens to every session and 6,481 once invoked, about $0.0008 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-30.

Related

Other skills, from other repositories

takt

TAKT ワークフローエンジン。codex exec でサブエージェントを起動し、ワークフロー YAML(steps / initialstep)に従って マルチエージェントオーケストレーションを実行する。.

nrslib/takt · 63 tokens

ship-and-babysit

End-to-end PR shipping workflow for tinyhumansai/openhuman: commit local changes, push to the user's fork, open or reuse a PR against main, then babysit CI and CodeRabbit feedback until the PR is green and clean. Use when the user asks to ship, open a PR, monitor CI, address review comments, or 'babysit' a branch.

tinyhumansai/openhuman · 83 tokens

company-product-context

Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.

lofcz/LLMTornado · 20 tokens

codebase-context-extractor

This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.

lofcz/LLMTornado · 42 tokens

Ability Generator

This skill generates markdown skill templates to be later used.

lofcz/LLMTornado · 14 tokens

release-feature-audit

Use when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — "audit #123", "审计这个功能", "这个 feature 过一遍检查" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks ("漏翻了吗", "检查 i18n"), which used to be…

haoxiang-xu/PuPu · 94 tokens