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 subscription-plan-changesgit 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/subscription-plan-changes)<a href="https://agentmods.dev/skills/appeeky/stripe-skills/subscription-plan-changes"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-skills/subscription-plan-changes.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.00050 | $0.00330 |
| Opus 5 | $0.00025 | $0.00165 |
| Sonnet 5 | $0.00010 | $0.00066 |
| Haiku 4.5 | $0.00005 | $0.00033 |
Grade A, and why
subscription-plan-changes 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 7d 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
Subscription Plan Changes
Stripe MCP Setup
Requires Stripe MCP connected via OAuth or restricted key. Docs: https://docs.stripe.com/mcp
GetMcpToolswithserver: "user-Stripe"(orplugin-stripe-stripe) before any call- Prefer
stripe_api_search→stripe_api_details→stripe_api_readfor list/retrieve - Always paginate —
limit: 100, followhas_morewithstarting_after - Amounts are in cents unless noted
- Never expose secret keys in output
Workflow
- Review codebase checkout update path (
subscriptions.updatevs new checkout) - Sample recent
customer.subscription.updated— compareitemsprice changes - Check proration:
proration_behavior, invoice line items forproration
Anti-Patterns
- Creating new subscription instead of updating → double billing
- No
alreadyOnPlanguard
Output Template
Plan Change Audit
Update method: in-place / new checkout
Proration: [behavior]
Recent migrations (sample):
| Customer | From → To | Proration $ |
Recommendations: ...
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.
- 7d ago First seen · 44 lines · 50 tokens per session scan A 17c0b048de8d
subscription-plan-changes is a skill published in the GitHub repository appeeky/stripe-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 330 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…