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 san-npm/skills-ws --skill stripe-billinggit clone --depth 1 https://github.com/san-npm/skills-wsWrote 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/san-npm/skills-ws/stripe-billing)<a href="https://agentmods.dev/skills/san-npm/skills-ws/stripe-billing"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/stripe-billing/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/san-npm/skills-ws/stripe-billing"><img src="https://agentmods.dev/badge/skills/san-npm/skills-ws/stripe-billing.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.00082 | $0.00951 |
| Opus 5 | $0.00041 | $0.00476 |
| Sonnet 5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
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 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Billing
Disambiguation: this skill = Next.js App Router + Server Actions. For Express/Node backends see
saas-billing.
Production patterns for Stripe billing that handle the edge cases tutorials skip. Subscription lifecycle, usage-based billing, webhook idempotency, EU VAT, and price migrations.
Critical principle: Webhooks are your source of truth, not API responses. Always design for eventual consistency.
Clover API invariants (this skill pins 2025-09-30.clover)
2025-09-30.clover is the first release of the Clover major line (majors run Acacia, Basil, Clover, Dahlia; breaking changes are cumulative, so Clover inherits Basil's). The first three invariants below were introduced in 2025-03-31.basil; the flexible billing_mode default is Clover's own change. The code below depends on these, so if you bump the version, re-verify at https://docs.stripe.com/changelog:
- Initial subscription payment secret lives at
latest_invoice.confirmation_secret.client_secret, NOTlatest_invoice.payment_intent. Expandlatest_invoice.confirmation_secret. (expand: ['latest_invoice.payment_intent']returns nothing on this version.) - Billing period fields moved to the subscription item: use
sub.items.data[0].current_period_end/current_period_start.sub.current_period_endno longer exists.billing_cycle_anchorstays on the subscription. - Legacy usage-based billing is removed:
aggregate_usageandbilling_thresholdsare gone;UsageRecord/UsageRecordSummaryendpoints are deleted. A metered price MUST reference a Billing Meter viarecurring.meter. Report usage withbilling.meterEvents.create. (Changelog: https://docs.stripe.com/changelog/basil/2025-03-31/deprecate-legacy-usage-based-billing) billing_mode: { type: 'flexible' }is the default for new subscriptions and is what enablesconfirmation_secret; set it explicitly so behavior is stable across version bumps.
Safety gate
Before executing commands or changing external systems, confirm scope, credentials, target environment, rollback, and required approval. Pin and verify third-party artifacts; never expose secrets to client code or logs.
What ships with it
13 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.
- agents/openai.yaml 168 B
- references/1-setup.md 1004 B
- references/10-testing.md 3.0 KB
- references/11-frontend-checkout.md 2.7 KB
- references/12-common-pitfalls.md 1.7 KB
- references/2-subscription-lifecycle.md 8.5 KB
- references/3-usage-based-billing-billing-meters.md 6.0 KB
- references/4-webhook-handler-production-grade.md 5.8 KB
- references/5-customer-portal.md 2.3 KB
- references/6-stripe-tax-for-eu-vat.md 3.4 KB
- references/7-adaptive-pricing.md 1.7 KB
- references/8-recovery-reconciliation-test-clocks.md 3.0 KB
- references/9-price-migration.md 2.8 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.
- 5d ago First seen · 44 lines · 82 tokens per session scan A 321d2fe687d4
stripe-billing is a skill published in the GitHub repository san-npm/skills-ws (2 stars, last pushed 5d ago), licensed MIT. It adds 82 tokens to every session and 951 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-09-07.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
tushare
A Python interface for Tushare, a financial data service that provides market and company information for stocks, funds, futures, and digital assets. It returns queried data as pandas tables.
stripe-best-practices
Guides Stripe integration decisions across development and test environment planning (separate sandboxes vs the shared test mode sandbox), API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, tax and registrations (Stripe Tax…
pinme-uniwebpay
Use when generating, modifying, or reviewing PinMe Worker (Cloudflare Worker TypeScript) code that accepts payments through UniwebPay — payment links, products/prices, checkout sessions, payment status reads, refunds, subscriptions, or handling UniwebPay webhooks with @uniwebpay/sdk in a PinMe project.
erp-xpp
X++ code development lifecycle for Finance and Operations — scaffold models, author classes, custom services/APIs, and data entities, install matching SDKs, compile deployable packages, deploy packages, synchronize databases, and verify deployed artifacts. Use when the user explicitly requests creating, building…
kalshi-api
Kalshi exchange mechanics — RSA-PSS auth, order schema, YES/NO orderbook convention, WebSocket, and endpoint surface. Market-type-agnostic shared layer for all Kalshi skills.