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 appeeky/stripe-skills --skill checkout-implementationgit clone --depth 1 https://github.com/appeeky/stripe-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/appeeky/stripe-skills/checkout-implementation)<a href="https://agentmods.dev/skills/appeeky/stripe-skills/checkout-implementation"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/checkout-implementation/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/skills/appeeky/stripe-skills/checkout-implementation"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/checkout-implementation.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.00065 | $0.00303 |
| Opus 5 | $0.00032 | $0.00151 |
| Sonnet 5 | $0.00013 | $0.00061 |
| Haiku 4.5 | $0.00006 | $0.00030 |
Grade A, and why
checkout-implementation 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.
What it actually says
Checkout Implementation
Builds Stripe payment flows matched to the project stack.
Choose the approach
| Need | Use |
|---|---|
| Fastest, hosted | Stripe Checkout (checkout.sessions.create) |
| Embedded, custom UI | Payment Element + PaymentIntent/SetupIntent |
| Recurring | subscription mode |
Checkout Session essentials
- mode: subscription
- line_items: price + quantity
- customer OR customer_email (reuse existing customer to avoid dupes)
- success_url / cancel_url
- allow_promotion_codes: true
- subscription_data metadata: user_id
- automatic_tax enabled (if using Stripe Tax)
Critical rules
- Reuse customer: check for existing
stripe_customer_id; for plan changes usesubscriptions.update(proration), never a 2nd subscription - Pass
user_idin metadata for webhook provisioning - Server-side price validation (whitelist price IDs)
Verify
stripe_implementation_planner (MCP) for architecture; test with test cards; confirm via webhook-implementation.
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 · 39 lines · 65 tokens per session scan A d94eb52cb52f
checkout-implementation is a skill published in the GitHub repository appeeky/stripe-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 303 once invoked, about $0.0003 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-31.
Other skills, from other repositories
marketplace-purchase-vetting
Use this when the user asks whether a local listing is a scam, "too good to be true," worth looking at, or a good deal. Also use this when he asks you to find options — search/discover candidates, then vet the best ones. The goal is not a generic buying guide; it is a practical risk read with clear next steps.
saas-billing
Implement and audit SaaS billing systems, subscription state machines, secure webhooks, and local database synchronization / Implementasi dan audit sistem billing SaaS, state machine langganan, webhook aman, dan sinkronisasi database lokal.
payment-gateway-expert
Expert guide for integrating payment gateways (Stripe, PayPal, Xendit, Midtrans, DOKU) and secure webhooks into SaaS platforms / Panduan ahli integrasi payment gateway dan webhook aman.
szamlazzhu-document-xml-compatibility
Integrate another WooCommerce plugin with Integration for Szamlazz.hu & WooCommerce document generation. Covers WCSzamlazz()->generateinvoice(), wcszamlazzxml, wcszamlazzinvoicelineitem, wcszamlazzbeforegenerateinvoicecheck, document meta, Action Scheduler deferral, Pro webhooks/IPN including HPOS-safe custom…
szamlazzhu-vat-checkout-compatibility
Make WooCommerce checkout, B2B, VAT/tax-number, address, and headless checkout code compatible with Integration for Szamlazz.hu & WooCommerce. Covers the classic checkout field wcszamlazzadoszam, order meta billingwcszamlazzadoszam and wcszamlazzadoszamdata, user meta wcszamlazzadoszam, Checkout Block/Store API…
wc-stripe-future-payments
Design or audit WooCommerce Stripe payment flows that save a reusable method and charge it later. Covers SetupIntent versus PaymentIntent, charge-now-and-save, deposits and installment series, setupfutureusage=offsession, Stripe Customer ownership, explicit consent/mandates, later off-session PaymentIntents, SCA…