CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/stripe-test-cards-and-webhooks

Wraps Stripe API testing patterns: test-mode initialization, the canonical test cards (4242 success; 4000 0000 0000 0002 declined; 4000 0027 6000 3184 3DS challenge per 3ds-test-flow-reference), the Stripe CLI webhook flow (`stripe listen --forward-to`), the Stripe CLI fixture commands (`stripe trigger payment_intent.succeeded`), and the webhook signature verification (Stripe-Signature header + HMAC-SHA256). Use when testing Stripe-integrated code.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Overview
Quality
Evals
Security
Files

Security

1 medium severity finding. This skill can be installed but you should review these findings before use.

Medium

W009: Direct money access capability detected (payment gateways, crypto, banking).

What this means

The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.

Why it was flagged

This skill is explicitly designed to interact with the Stripe payment gateway: it shows initializing the Stripe SDK with API keys and contains concrete calls to create PaymentIntents (stripe.paymentIntents.create), idempotent payment creation, and Stripe CLI commands (stripe listen, stripe trigger). Those are specific payment-gateway operations (even if shown for test-mode), which constitute Direct Financial Execution capability.

Report incorrect finding
Audited
Security analysis
Snyk