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 commands/ncklrs/claude-chrome-user-testing/ab-testgit clone --depth 1 https://github.com/ncklrs/claude-chrome-user-testingWrote 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/commands/ncklrs/claude-chrome-user-testing/ab-test)<a href="https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/ab-test"><img src="https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/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.00032 | $0.02344 |
| Opus 5 | $0.00016 | $0.01172 |
| Sonnet 5 | $0.00006 | $0.00469 |
| Haiku 4.5 | $0.00003 | $0.00234 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A/B Testing Command
Compare two URL variants with the same persona to determine which version provides a better user experience. Useful for testing redesigns, feature flags, staging vs production, or any design variations.
Arguments
Parse the following from $ARGUMENTS:
--url-a <url>(required): Variant A URL (typically control/current version)--url-b <url>(required): Variant B URL (typically test/new version)--persona <id>(required unless --personas used): Single persona to test with--personas <ids>(optional): Comma-separated persona IDs for multi-persona A/B testing--tasks <tasks>(optional): Comma-separated tasks to perform on each variant--gender <m|f|n>(optional): Gender variant (male/female/neutral)--quiet(optional): Disable narration, show only comparison summary--record(optional): Record sessions as Playwright Traces--record-path <path>(optional): Custom output path for trace files (default: recordings/)--viewport <mobile|tablet|desktop>(optional): Device viewport size (default: desktop)--output <markdown|json>(optional): Report output format (default: markdown)--network <slow-3g|fast-3g|offline>(optional): Network throttling preset--pr <number>(optional): Post results as GitHub PR comment
Pre-Flight Checklist
Before beginning the test, verify:
- Chrome Integration: Confirm Claude is running with
--chromeflag - Both URLs Accessible: Navigate to both URLs and verify they load
- Persona Loading: Load the specified persona configuration
- Variant Labels: Identify Variant A as "Control" and Variant B as "Test"
A/B Testing Flow
Phase 1: Setup
"I'm going to test two versions of this site as [Persona Name].
- Variant A (Control): [URL A]
- Variant B (Test): [URL B]
Let me start with Variant A..."
Phase 2: Test Variant A
- Navigate to Variant A URL
- Perform all specified tasks (or free exploration)
- Collect:
- Task completion status
- Issues found (critical/major/minor)
- Confusion events
- Frustration trigger matches
- Screenshots at key moments
- Generate internal results for Variant A
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.
- 6d ago First seen · 312 lines · 32 tokens per session scan A 8e57d71cd87a
ab-test is a command published in the GitHub repository ncklrs/claude-chrome-user-testing (19 stars, last pushed 8mo ago), licensed MIT. It adds 32 tokens to every session and 2,344 once invoked, about $0.0002 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.
Other commands, from other repositories
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
wp-clone
Clone a remote or staging WordPress site to a local development environment.
wp-tailwindify
Convert an HTML/CSS demo to Tailwind-native HTML — preserves section delimiters, maps colors to @theme variables.
wp-contribute
Contributor workflow for the plugin itself — scaffold a command/agent/skill with its check and doc rows, verify the repo, or open the PR in the house format.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.