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.
git 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/smoke-test)<a href="https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/smoke-test"><img src="https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/smoke-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.00029 | $0.01628 |
| Opus 5 | $0.00015 | $0.00814 |
| Sonnet 5 | $0.00006 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
smoke-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 8d 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Smoke Test Command
Run pre-built test configurations for common user flows. Each preset uses an appropriate default persona and validates specific functionality.
Arguments
Parse the following from $ARGUMENTS:
--url <url>(required): Target URL to test--preset <preset>(required): Preset name to run--persona <id>(optional): Override the default persona--gender <m|f|n>(optional): Gender variant--quiet(optional): Summary only, no narration--record(optional): Record session as Playwright Trace--record-path <path>(optional): Custom trace output path--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
Available Presets
| Preset | Default Persona | What It Tests |
|---|---|---|
login |
busy-executive | Authentication flow works |
signup |
genz-digital-native | Registration flow works |
checkout |
impulse-buyer | Purchase flow works |
navigation |
boomer-tech-averse | Site navigation works |
search |
power-user | Search functionality works |
Preset Details
login
Tests the authentication flow:
- Find login link/button
- Navigate to login page
- Enter test credentials
- Submit login form
- Verify successful login (dashboard, welcome message, etc.)
Default Persona: busy-executive (expects quick, efficient login)
Success Criteria:
- Login form is accessible
- Form accepts credentials
- User is logged in after submission
signup
Tests the registration flow:
- Find signup/register link
- Navigate to signup page
- Complete registration form
- Submit form
- Verify account creation
Default Persona: genz-digital-native (expects minimal friction)
Success Criteria:
- Signup form is accessible
- Form fields are clear
- Registration completes successfully
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.
- 8d ago First seen · 278 lines · 29 tokens per session scan A 048a4b70416b
smoke-test is a command published in the GitHub repository ncklrs/claude-chrome-user-testing (19 stars, last pushed 8mo ago), licensed MIT. It adds 29 tokens to every session and 1,628 once invoked, about $0.0001 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
ios-test
Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.
paul:verify
Guide manual user acceptance testing of recently built features.
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
verify-pr
Verify a PR's frontend changes through browser automation.
harness-eval
A four-level verification command for completed software tasks. It checks whether the code builds, matches its documented contracts, works end to end, and follows the project's governing rules.
test-run
Run E2E tests with qa-use CLI.