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 usage-based-billinggit 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/usage-based-billing)<a href="https://agentmods.dev/skills/paddlehq/paddle-agent-skills/usage-based-billing"><img src="https://agentmods.dev/badge/skills/paddlehq/paddle-agent-skills/usage-based-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/paddlehq/paddle-agent-skills/usage-based-billing"><img src="https://agentmods.dev/badge/skills/paddlehq/paddle-agent-skills/usage-based-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.00055 | $0.06668 |
| Opus 5.5 | $0.00022 | $0.02667 |
| Sonnet 5.5 | $0.00011 | $0.01334 |
| Haiku 4.5 | $0.00006 | $0.00667 |
Grade A, and why
paddle-usage-based-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 — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add usage-based billing to a Next.js app (early access)
When to use this skill
Use this skill when the user wants subscription plans that include prepaid usage — like 10,000 API calls, 1 million tokens, or 500 document exports a month — and wants to report usage to Paddle and restrict features when customers run out.
Pair with:
catalog-setup— create the product. Create prices with allowances using this skill's API helper instead of its seed script, and don't reuse its trial price: prices with allowances can't have a trial period.checkout-web— customers subscribe to a plan with an allowance using a normal checkout.subscription-sync— map your users to Paddle customer IDs, which usage events need.webhooks— receive and verifyusage_balance.depleted, and queue work instead of doing it in the handler.subscription-update— plan changes. This skill overrides its proration defaults (see "Renewals and plan changes").sandbox-testing— test cards and checkout in a sandbox account.
Early access (beta) status and tooling
Read this first. These facts change how you build the integration.
- Get the latest version of this skill before you start. Early access (beta) changes often, so this copy might be out of date. Fetch the latest version and follow it instead if it's different. If you can't, continue with this copy, and suggest the user updates their Paddle plugin or skills.
- Usage-based billing is in early access (beta). Only accounts in the early access program can use it, and fields and behavior may change before general release. Accounts apply at Set up usage-based billing.
- The Paddle MCP servers don't include usage-based billing operations during early access (beta). Don't
searchthe MCP for meter, usage event, or usage balance tools, and don't fake metering with custom items or one-time charges. Call the Paddle API withfetch, as shown below. - The Paddle Node SDK doesn't support usage-based billing yet. It has no
paddle.metersorpaddle.usageEvents, and its price types don't includeallowances: TypeScript rejects the field onpaddle.prices.create(), and the SDK'sPriceobjects leave it out of responses. Usefetchfor every call in this skill. Use the SDK only to verify webhooks. - Paddle never blocks usage during early access (beta). When a balance runs out, Paddle keeps recording usage as overage and doesn't bill for it. Your app decides what customers can do.
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 First seen · 511 lines · 55 tokens per session scan A 85ae8426cdd3
paddle-usage-based-billing is a skill published in the GitHub repository PaddleHQ/paddle-agent-skills (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 6,668 once invoked, about $0.0002 per session on Opus 5.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-10-17.
Other skills, from other repositories
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
food-order
Reorder previous Foodora orders, preview cart contents, and track delivery ETA/status with ordercli. Use when the user wants to reorder food, check delivery status, or browse recent Foodora order history. Never confirm an order without explicit user approval.
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
Product Photoshoot Workflow
A workflow for turning one product photo into a set of four e-commerce images from different visual directions.
cloudbase-wechat-integration
A guide for connecting CloudBase applications to WeChat services, including payments, official accounts, and user identity.