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 skills add ncklrs/claude-chrome-user-testing --skill ab-testinggit 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/skills/ncklrs/claude-chrome-user-testing/ab-testing)<a href="https://agentmods.dev/skills/ncklrs/claude-chrome-user-testing/ab-testing"><img src="https://agentmods.dev/badge/skills/ncklrs/claude-chrome-user-testing/ab-testing.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.00000 | $0.02114 |
| Opus 5 | $0.00000 | $0.01057 |
| Sonnet 5 | $0.00000 | $0.00423 |
| Haiku 4.5 | $0.00000 | $0.00211 |
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 7d 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 — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.
A/B Testing Skill
Compare two URL variants with the same persona to determine which provides a better user experience. This skill guides the comparison logic and report generation.
When to Use
- Comparing a redesign against current production
- Testing feature flag variations
- Evaluating staging vs production differences
- Comparing different UX approaches
Core Concept
Multi-Persona Testing: Same URL + Different Personas → Compare user types
A/B Testing: Same Persona + Different URLs → Compare design variants
Comparison Metrics
Track these metrics for each variant:
| Metric | Better When | Comparison |
|---|---|---|
| Tasks Completed | Higher | X/Y vs X/Y |
| Critical Issues | Lower | Count vs Count |
| Major Issues | Lower | Count vs Count |
| Minor Issues | Lower | Count vs Count |
| Confusion Events | Lower | Count vs Count |
| Frustration Triggers | Lower | Count vs Count |
Winner Determination
Per-Metric Winner
function getMetricWinner(metricName, valueA, valueB) {
// For issues/confusion/frustration: lower is better
if (['criticalIssues', 'majorIssues', 'minorIssues',
'confusionEvents', 'frustrationTriggers'].includes(metricName)) {
if (valueA < valueB) return 'A';
if (valueB < valueA) return 'B';
return 'Tie';
}
// For task completion: higher is better
if (metricName === 'tasksCompleted') {
if (valueA > valueB) return 'A';
if (valueB > valueA) return 'B';
return 'Tie';
}
return 'Tie';
}
Overall Winner
function getOverallWinner(results) {
let aWins = 0;
let bWins = 0;
for (const metric of results.metrics) {
if (metric.winner === 'A') aWins++;
if (metric.winner === 'B') bWins++;
}
if (aWins > bWins) return 'A';
if (bWins > aWins) return 'B';
// Tiebreaker: task completion
const taskA = results.variantA.tasksCompleted;
const taskB = results.variantB.tasksCompleted;
if (taskA > taskB) return 'A';
if (taskB > taskA) return 'B';
return 'Tie';
}
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.
- 7d ago First seen · 338 lines · 0 tokens per session scan A 09625d28a424
ab-testing is a skill published in the GitHub repository ncklrs/claude-chrome-user-testing (19 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,114 tokens. 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 skills, from other repositories
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
Accessibility Auditor
Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.
Accessibility A11y Enhanced
Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.
Axe-core Accessibility Testing
Accessibility testing skill using axe-core and Playwright for automated WCAG 2.1 compliance auditing, custom rules, and accessibility reporting.
axe-core Accessibility Automation
Automated accessibility testing with axe-core integrated into CI pipelines, including custom rule configuration, issue prioritization, and remediation guidance.
agent-evaluation-operations
Evaluate agent and skill behavior or routing.