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/xiaoyuge886/aigcWrote 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/xiaoyuge886/aigc/test-cards)<a href="https://agentmods.dev/commands/xiaoyuge886/aigc/test-cards"><img src="https://agentmods.dev/badge/commands/xiaoyuge886/aigc/test-cards.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.00009 | $0.00233 |
| Opus 5 | $0.00005 | $0.00117 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
test-cards 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.
This is a copy
100% identical to test-cards — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Test Cards Reference
Provide a quick reference for Stripe test card numbers:
- If a scenario argument is provided (e.g., "declined", "3dsecure", "fraud"), show relevant test cards for that scenario
- Otherwise, show the most common test cards organized by category:
- Successful payment (default card)
- 3D Secure authentication required
- Generic decline
- Specific decline reasons (insufficient_funds, lost_card, etc.)
- For each card, display:
- Card number (formatted with spaces)
- Expected behavior
- Expiry/CVC info (any future date and any 3-digit CVC)
- Use clear visual indicators (✓ for success, ⚠️ for auth required, ✗ for decline)
- Mention that these only work in test mode
- Provide link to full testing documentation: https://docs.stripe.com/testing.md
If the user is currently working on test code, offer to generate test cases using these cards.
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 · 25 lines · 9 tokens per session scan A 4e2496258654
test-cards is a command published in the GitHub repository xiaoyuge886/aigc (197 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 233 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to test-cards, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
verify
Run repository verification using the verification-loop skill.
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.