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 PaddleHQ/paddle-agent-skills --skill subscription-updategit clone --depth 1 https://github.com/PaddleHQ/paddle-agent-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/paddlehq/paddle-agent-skills/subscription-update)<a href="https://agentmods.dev/skills/paddlehq/paddle-agent-skills/subscription-update"><img src="https://agentmods.dev/badge/skills/paddlehq/paddle-agent-skills/subscription-update/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/paddlehq/paddle-agent-skills/subscription-update"><img src="https://agentmods.dev/badge/skills/paddlehq/paddle-agent-skills/subscription-update.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.00048 | $0.03778 |
| Opus 5 | $0.00024 | $0.01889 |
| Sonnet 5 | $0.00010 | $0.00756 |
| Haiku 4.5 | $0.00005 | $0.00378 |
Grade A, and why
paddle-subscription-update 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 10d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update a Paddle subscription's plan from Next.js
When to use this skill
Use this skill when building "Upgrade plan," "Switch tier," or "Change subscription" actions in your authenticated user's billing UI. It covers a Next.js 15 (App Router) Server Action that calls paddle.subscriptions.update(), the four prorationBillingMode choices and when to pick each, the replace not append semantics of the items array, and the security checks every plan-change action needs.
This is the initiating side of subscription changes. Pair it with:
subscription-sync— your webhook handler will get asubscription.updatedevent after the change. Your DB mirror picks up the new plan, status, and pricing.subscription-cancel— same auth/ownership shape; if you're building both, share the helpers.
Prerequisites
- A Paddle account with at least two prices the user can switch between (e.g. monthly Starter and monthly Pro). Sandbox is fine.
- Server-side
PADDLE_API_KEYavailable — Server Action only. - Customer + subscription state mirrored from webhooks (see
subscription-sync). - An auth system. Examples use Supabase.
NEXT_PUBLIC_PADDLE_ENV=sandbox # or "production"
PADDLE_API_KEY=pdl_sdbx_apikey_...
NEXT_PUBLIC_SUPABASE_URL=...
NEXT_PUBLIC_SUPABASE_ANON_KEY=...
SUPABASE_SERVICE_ROLE_KEY=... # or SUPABASE_SECRET_KEY (new opaque sb_secret_*)
Choose your prorationBillingMode
This is the one parameter most people get wrong. Paddle's subscriptions.update accepts five values; for a typical "Upgrade to Pro" flow the right choice is prorated_immediately.
| Value | What happens | When to use |
|---|---|---|
prorated_immediately |
Charge the prorated difference between old and new plan now, switch effective immediately. | "Upgrade plan" — user expects access to the new plan + a charge now. |
prorated_next_billing_period |
Calculate the prorated amount but bill it on the next renewal. Plan switch is immediate. | "Switch plan, but bill me later" — rare, but legitimate. |
full_immediately |
Charge the full new-plan price now. Plan switch is immediate. | Not often. Over-charges the user for a partial period. |
full_next_billing_period |
Charge full new-plan price on next renewal. Plan switch is immediate. | "Try the new plan free until renewal" — uncommon but legitimate. |
do_not_bill |
Switch plans now. Don't bill anything. | Internal/team upgrades, customer service comps. Never for self-serve UX. |
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.
- 10d ago First seen · 242 lines · 48 tokens per session scan A baa8cfc235a0
paddle-subscription-update is a skill published in the GitHub repository PaddleHQ/paddle-agent-skills (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 48 tokens to every session and 3,778 once invoked, about $0.0002 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
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 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…
erp-xpp
Finance and Operations X++ development lifecycle — 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 wants to create, build, compile, package, deploy…
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.
tushare-plugin-builder
This skill should be used when the user provides a Tushare API document URL and asks to generate a full plugin in this codebase, including extractor, schema, config, query service, and agent/MCP/http usage with testable curl examples.