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/stripe-test)<a href="https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/stripe-test"><img src="https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/stripe-test/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/stripe-test"><img src="https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/stripe-test.svg" alt="Reviewed on agentmods" width="80" 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.00026 | $0.01984 |
| Opus 5.5 | $0.00010 | $0.00794 |
| Sonnet 5.5 | $0.00005 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
stripe-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 1mo 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Checkout Test Command
Test Stripe payment flows with persona-based user simulation. Uses official Stripe test cards to simulate various payment scenarios.
Arguments
Parse the following from $ARGUMENTS:
--url <url>(required): Checkout or product page URL--persona <id>(optional): Persona to use (default: impulse-buyer)--personas <ids>(optional): Comma-separated persona IDs for parallel testing--gender <m|f|n>(optional): Gender variant--card <scenario>(optional): Test card scenario (default: success)--email <email>(optional): Email for checkout (default: [email protected])--tasks <tasks>(optional): Tasks to perform before checkout--quiet(optional): Disable narration, show only summary and screenshots--record(optional): Record the session as a Playwright Trace for replay--record-path <path>(optional): Custom output path for trace file (default: recordings/)
Test Card Scenarios
| Scenario | Description | Use Case |
|---|---|---|
success |
Payment succeeds | Happy path testing |
decline |
Generic decline | Error handling |
insufficient |
Insufficient funds | Specific decline message |
lost |
Lost card | Specific decline message |
stolen |
Stolen card | Specific decline message |
expired |
Expired card | Expiry validation |
cvc-fail |
CVC check fails | CVC validation |
processing-error |
Processing error | Server error handling |
3ds-required |
3D Secure required | Authentication flow |
3ds-optional |
3D Secure optional | Optional auth handling |
fraud-high |
High fraud risk | Radar blocking |
visa-debit |
Visa debit card | Debit card acceptance |
mastercard |
Mastercard | Card brand testing |
amex |
American Express | Amex (4-digit CVC) |
Pre-Flight Checklist
Before testing:
- Chrome Integration: Verify
claude --chromeis active - URL Accessible: Navigate to target URL
- Persona Loading: Load specified persona (default: impulse-buyer)
- Test Card Ready: Load card data from
skills/stripe-checkout/test-cards.json
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.
- 1mo ago First seen · 303 lines · 26 tokens per session scan A a378e73e5327
stripe-test is a command published in the GitHub repository ncklrs/claude-chrome-user-testing (21 stars, last pushed 9mo ago), licensed MIT. It adds 26 tokens to every session and 1,984 once invoked, about $0.0001 per session on Opus 5.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
gate
Run every objective gate this project can prove and report the real N/N. Use before claiming any screen or component is done.
wp-responsive-check
Responsive validation — screenshots at 9 viewports, checks for layout issues.
checkout-specialist
Use when a cart or checkout is losing people. Abandoned carts, long payment forms, forced account creation, shipping cost revealed too late, weak trust signals, confusing order confirmation.
wake-test-plan
Generate a test plan for a Wake Commerce storefront feature. Defines E2E scenarios, contract tests, and acceptance criteria. Delegates detailed test design to the wake-qa-expert agent.
test-strategy
Write a test strategy as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
ios-test
Bu komut iOS/SwiftUI uygulamasini derleyip simulator'da acarak computer use ile gorsel test yapar.