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 ssheleg/sheleg-dev --skill stripe-billinggit clone --depth 1 https://github.com/ssheleg/sheleg-devWrote 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/ssheleg/sheleg-dev/stripe-billing)<a href="https://agentmods.dev/skills/ssheleg/sheleg-dev/stripe-billing"><img src="https://agentmods.dev/badge/skills/ssheleg/sheleg-dev/stripe-billing.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.00211 | $0.04457 |
| Opus 5 | $0.00105 | $0.02228 |
| Sonnet 5 | $0.00042 | $0.00891 |
| Haiku 4.5 | $0.00021 | $0.00446 |
Grade A, and why
stripe-billing 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 yesterday.
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 — 399 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe billing
Stripe holds the money. Your database holds the entitlement. Every serious billing defect is one fact living in two systems that stopped agreeing — a price, a quantity, a period, a refunded total.
Stripe's API is not where integrations fail. Failures happen at the seam: the callback that arrived twice, the renewal that granted a month of product for a $0.40 proration invoice, the upgrade that charged the card and then failed to write the row.
This skill is that seam. For which Stripe primitive to use, the official
stripe-best-practices skill is the authority and wins any disagreement; for
lookups, stripe-docs. Examples are TypeScript; the rules are
language-neutral.
Deep material, loaded on demand:
| Read | When |
|---|---|
references/stripe-agent-toolchain.md |
starting from nothing, or about to guess an API shape — CLI, MCP, skills index, key handling |
references/webhook-events.md |
writing or reviewing the handler — event catalogue, payload shapes, ordering, failure semantics |
references/subscription-lifecycle.md |
implementing checkout, verify, renewal, seats, plan change, trials, clawback |
references/cancellation-and-retention.md |
implementing cancel or reactivation, or offering a coupon at the cancel step |
references/price-integrity.md |
pricing lives in more than one file, or an advertised price must be proved against Stripe |
references/testing-and-local-dev.md |
local webhooks and mocks, and the shipped fixtures/ — the suite, already written |
references/provider-concentration.md |
growing revenue, opening a second market, separating involuntary churn, or if the payment account is limited |
Start with Stripe's own tooling
What ships with it
24 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.
- fixtures/assert-money-invariants.mjs 30 KB runs code
- fixtures/charge-refunded-partial.json 1.3 KB
- fixtures/charge-refunded-remainder.json 1.7 KB
- fixtures/checkout-session-async-payment-failed.json 1.2 KB
- fixtures/checkout-session-completed-async-unpaid.json 1.1 KB
- fixtures/checkout-session-completed-paid.json 1.2 KB
- fixtures/customer-discount-created-retention.json 1.3 KB
- fixtures/customer-subscription-updated-cancel-classic.json 1.7 KB
- fixtures/customer-subscription-updated-cancel-flexible.json 1.7 KB
- fixtures/customer-subscription-updated-discount-consumed.json 1.7 KB
- fixtures/invoice-paid-subscription-cycle-next-period.json 1.9 KB
- fixtures/invoice-paid-subscription-cycle-redelivery.json 1.9 KB
- fixtures/invoice-paid-subscription-cycle.json 1.8 KB
- fixtures/invoice-paid-subscription-update-proration.json 2.5 KB
- fixtures/manifest.json 5.8 KB
- fixtures/README.md 9.3 KB
- fixtures/reference-handler.mjs 19 KB runs code
- references/cancellation-and-retention.md 21 KB
- references/price-integrity.md 8.4 KB
- references/provider-concentration.md 6.8 KB
- references/stripe-agent-toolchain.md 7.8 KB
- references/subscription-lifecycle.md 14 KB
- references/testing-and-local-dev.md 11 KB
- references/webhook-events.md 12 KB
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.
- yesterday Changed · -3 lines a0dcc36937f5
- 7d ago First seen · 402 lines · 211 tokens per session scan A 9c161f4e9247
stripe-billing is a skill published in the GitHub repository ssheleg/sheleg-dev (2 stars, last pushed today), licensed MIT. It adds 211 tokens to every session and 4,457 once invoked, about $0.0011 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
stripe-best-practices
Guides Stripe integration decisions across API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax, automatictax, product tax codes), Treasury financial accounts, integration options (Checkout, Payment…
tiun-sdk
Use when integrating or debugging the tiun SDK (@tiun/sdk), tiun's JavaScript library for authentication, subscription billing, one-time purchases, and time-based paywalls. Triggers on imports of @tiun/sdk, calls like tiun.init, tiun.checkout, tiun.login, tiun.start, or questions about tiun products, entitlements…
Stripe Payments
Automate Stripe payment processing, subscription management, invoicing, and financial reporting.
monetization
Estrategia e implementacao de monetizacao para produtos digitais - Stripe, subscriptions, pricing experiments, freemium, upgrade flows, churn prevention, revenue optimization e modelos de negocio SaaS.
stripekit
Add Stripe billing — subscriptions, checkout, and the customer portal — to an app by declaring a catalog in code and running the stripekit CLI. Use when a user wants to add payments, subscriptions, plans, pricing, checkout, or a billing portal with Stripe (especially in a Next.js app), or to manage Stripe…
pricing-products-audit
Maps Stripe products and prices — plans, intervals, amounts, active vs archived, and which prices appear on live subscriptions. Use when the user asks "what products do we sell", "price IDs", "pricing tiers", "plan structure", or "where does revenue go".