creating-ab-test

creating-ab-test is a skill for Claude Code from SwiftfulThinking/SwiftfulStarterProject. It costs 64 tokens per session (859 once invoked), scanned A, original, MIT.

A procedure for adding an A/B test, an experiment that compares two or more versions of a feature with different users. It wires either an on/off setting or a choice among several options through the app's test, settings, and remote-configuration code.

In plain words
What is it for?
Use it to add feature flags, remote configuration tests, or experiments and connect them to active-test data, services, developer settings, and the app's core logic.
Why use it?
It prevents a new experiment from being added in only one place while other parts of the app cannot read or change it.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to add feature flags, remote configuration tests, or experiments and…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swiftfulthinking/swiftfulstarterproject/creating-ab-test
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 SwiftfulThinking/SwiftfulStarterProject --skill creating-ab-test
Clone the repo
git clone --depth 1 https://github.com/SwiftfulThinking/SwiftfulStarterProject

Made for: Claude Code.

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 creating-ab-test

README.md
[![agentmods](https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-ab-test.svg)](https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-ab-test)
Your own site
<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-ab-test"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-ab-test.svg" alt="Measured on agentmods" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 859 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.00064 $0.00859
Opus 5 $0.00032 $0.00430
Sonnet 5 $0.00013 $0.00172
Haiku 4.5 $0.00006 $0.00086

Measured yesterday against content hash 40d6306ba44a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

creating-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 yesterday.

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.

.claude/skills/creating-ab-test/SKILL.md · 59 lines

How it starts

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

Creating AB Test

Wire a new AB test through all required files. This is a multi-file mechanical change — every test follows the same pattern across 5+ files.

Steps

  1. Get the test name from the user (camelCase, e.g., showBanner, paywallVariant)
  2. Determine the test type — Bool (on/off) or enum (multiple variants)
  3. If enum, create the option enum file first
  4. Read references/checklist.md for the exact code to add in each file
  5. Update all files in order

Test Type

Type When Example
Bool Simple on/off flag showBanner: Bool
Enum Multiple variants paywallVariant: PaywallTestOption

For enum tests, create a {TestName}Option.swift file in Managers/ABTests/Models/ with String, Codable, CaseIterable conformance and a static var default.

Files to Update (in order)

# File What to Add
1 Managers/ABTests/Models/ActiveABTests.swift Property, init param, CodingKey, eventParameters, update method, RemoteConfig init, asNSObjectDictionary
2 All files in Managers/ABTests/Services/ Each service conforming to ABTestService must be updated to handle the new test property (see below)
3 Core/DevSettings/DevSettingsPresenter.swift State property, loadABTests line, change handler
4 Core/DevSettings/DevSettingsView.swift Toggle (Bool) or Picker (enum) in abTestSection
5 Root/RIBs/Core/CoreInteractor.swift Computed property exposing the test value

Updating Service Files

List all files in Managers/ABTests/Services/ and update every one. The specific services may vary by project (e.g., MockABTestService, LocalABTestService, FirebaseABTestService, MixpanelABTestService, etc.). For each service, read the file and add the new test property following its existing pattern — mock services get an optional init param, local services get a @UserDefault, prod services get a default value.

Read the full file on GitHub · 59 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. yesterday First seen · 59 lines · 64 tokens per session scan A 40d6306ba44a

Subscribe to this mod's changes

creating-ab-test is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 859 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-09-04.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens