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 agentmods add skills/cookiemonsterdev/agents-skills/stripe-docsnpx skills add cookieMonsterDev/agents-skills --skill stripe-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-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/cookiemonsterdev/agents-skills/stripe-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/stripe-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/stripe-docs.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.00071 | $0.01223 |
| Opus 5 | $0.00036 | $0.00611 |
| Sonnet 5 | $0.00014 | $0.00245 |
| Haiku 4.5 | $0.00007 | $0.00122 |
Grade A, and why
stripe-docs 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe questions carry real financial and compliance risk if answered from stale memory, since API versions, webhook event names, and integration patterns change frequently. Use this skill to ground answers in the official Stripe documentation and return the closest authoritative page instead of generic payments advice.
When to Use
Use this skill when the request is about:
- Payments: Payment Intents, Checkout, Elements, payment methods, and Terminal (in-person)
- Billing and revenue: subscriptions, invoices, usage-based pricing, tax, and the customer portal
- Connect: marketplace and platform payments, onboarding, charges, and payouts to connected accounts
- Webhooks: event types, signature verification, and idempotent event handling
- API usage: authentication, idempotency keys, error codes, versioning, and rate limits
- SDKs and client libraries for server-side and client-side integration
- Testing: test mode, test card numbers, the Stripe CLI, and webhook simulation
- Security and compliance: API key management, PCI scope, Radar fraud detection, and Identity verification
- Stripe Tax, Stripe Issuing, Stripe Treasury, and other adjacent Stripe products
Do not use this skill for:
- Generic e-commerce or checkout UX design unless the question is specifically about Stripe's prebuilt components (Checkout, Elements, Payment Links).
- Other payment processors (PayPal, Adyen, Braintree) unless the user is explicitly comparing them to Stripe.
- Tax law or accounting questions beyond what Stripe Tax or Stripe's revenue recognition docs directly document.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started, development environment, and quickstarts
- Core payments (Payment Intents, Checkout, Elements, payment methods)
- Billing and subscriptions
- Connect (marketplaces and platforms)
- Webhooks and event handling
- API reference, authentication, and idempotency
- Testing and the Stripe CLI
- Security, compliance, and fraud prevention (Radar, Identity)
What ships with it
2 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.
- 5d ago First seen · 103 lines · 71 tokens per session scan A 44ed707125cd
stripe-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (4 stars, last pushed 16d ago), licensed MIT. It adds 71 tokens to every session and 1,223 once invoked, about $0.0004 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…