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 petrkindlmann/qa-skills --skill payment-testinggit clone --depth 1 https://github.com/petrkindlmann/qa-skillsWrote 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/petrkindlmann/qa-skills/payment-testing)<a href="https://agentmods.dev/skills/petrkindlmann/qa-skills/payment-testing"><img src="https://agentmods.dev/badge/skills/petrkindlmann/qa-skills/payment-testing.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
- NVIDIA SkillSpector pass
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.00192 | $0.04864 |
| Opus 5 | $0.00096 | $0.02432 |
| Sonnet 5 | $0.00038 | $0.00973 |
| Haiku 4.5 | $0.00019 | $0.00486 |
Grade A, and why
payment-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 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Route
| You need to test… | Go to | Reference |
|---|---|---|
| Success / decline / insufficient-funds outcomes | Test cards | references/stripe-test-cards.md |
| A 3DS/SCA challenge that pops a modal | 3DS challenge | references/playwright-3ds.md |
| A subscription renewal months/years out | Test clocks | references/webhooks-and-clocks.md |
| Webhooks reaching localhost + signatures | Webhooks | references/webhooks-and-clocks.md |
| A failed renewal then a refund | Failed payments | references/webhooks-and-clocks.md |
| Fulfillment only after real payment | Reconciliation | references/webhooks-and-clocks.md |
| Adyen / PayPal / Braintree sandboxes | Multi-PSP | references/multi-psp.md |
Discovery Questions
First, check .agents/qa-project-context.md in the project root and skip anything it
already answers (PSP, stack, test framework, existing fixtures). Then clarify:
- Which PSP, and is it Stripe? Stripe is the default here. Other PSPs share the pattern but have their own sandbox cards/accounts — see Multi-PSP.
- One-time payments, subscriptions, or both? Subscriptions pull in test clocks, dunning,
and the
invoice.*lifecycle; one-time payments don't. - Is SCA/3DS in play? EU/UK card flows almost always challenge. If yes you need the nested-iframe pattern, not plain locators.
- Do you fulfill on a webhook or on the redirect today? If fulfillment happens on
return_url, that's the bug to test for — fulfillment must wait for the verified webhook. - Where does the webhook handler run in tests? Local (
stripe listen) vs a deployed preview env changes how you deliver events.
What ships with it
4 files 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.
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 · 373 lines · 192 tokens per session scan A 36dada06d6d0
payment-testing is a skill published in the GitHub repository petrkindlmann/qa-skills (113 stars, last pushed 2mo ago), licensed MIT. It adds 192 tokens to every session and 4,864 once invoked, about $0.0010 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 skills, from other repositories
synthetic-monitoring
AI-powered synthetic monitoring skill for e-commerce websites. Designs automated user journey tests for add-to-cart, checkout, and payment flows with alerting rules and performance baselines.
visual-regression-testing
AI-powered visual regression testing skill for e-commerce websites. Designs screenshot comparison workflows, mobile/desktop visual checks, and change detection alerts to prevent conversion-killing UI bugs.
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.
Angry User Simulator
Simulate aggressive user behavior patterns including rapid clicking, random navigation, form abuse, tab spamming, and unexpected interaction sequences to find UI resilience issues.
First-Time User Tester
Validate the first-time user experience including onboarding flows, empty states, tutorial completion, progressive disclosure, and initial setup wizards.
Console Error Hunter
Systematically detect, capture, and categorize browser console errors, warnings, and unhandled exceptions during automated test execution.