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 usage-based-billinggit 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/usage-based-billing)<a href="https://agentmods.dev/skills/appeeky/stripe-skills/usage-based-billing"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-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/appeeky/stripe-skills/usage-based-billing"><img src="https://agentmods.dev/badge/skills/appeeky/stripe-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.00077 | $0.00430 |
| Opus 5.5 | $0.00031 | $0.00172 |
| Sonnet 5.5 | $0.00015 | $0.00086 |
| Haiku 4.5 | $0.00008 | $0.00043 |
Grade A, and why
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 2mo 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
Usage-Based Billing
Stripe MCP Setup
Requires Stripe MCP (https://docs.stripe.com/mcp). GetMcpTools before CallMcpTool. Paginate all lists (limit: 100, starting_after while has_more). Amounts in cents. Read-only for audits; confirm before writes.
Concepts
| Model | Setup |
|---|---|
| Pure metered | Meter + usage-based price; bill actual usage |
| Prepaid credits | Credit grant burns down with usage |
| Hybrid | Base subscription + overage above included quota |
Modern Stripe uses Meters + Meter Events (billing/meter-events), replacing legacy usage records.
Workflow
- Review prices:
GetPrices-- look for metered usage_type / meter-linked - Check meter definitions (Dashboard -> Billing -> Meters)
- Verify usage reporting path in code (meter events sent on each usage)
Design Checklist
- Meter defined with aggregation (sum/count/last)
- Price linked to meter
- Usage events sent reliably (idempotent, retried)
- Included quota vs overage tiers defined
- Customer-facing usage visibility
Output Template
Usage Billing Audit
Metered prices: [n]
Meters: [list + aggregation]
Usage reporting: [reliable / gaps]
Model: [pure metered / credits / hybrid]
Recommendation: [tiering / quota / reliability fix]
For complex credit/commit models, note Metronome + Stripe pattern (see Stripe docs).
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.
- 2mo ago First seen · 52 lines · 77 tokens per session scan A b0dbd5e272b3
usage-based-billing is a skill published in the GitHub repository appeeky/stripe-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 430 once invoked, about $0.0003 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-08-31.
usage-based-billing compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| usage-based-billingappeeky/stripe-skills | Skill | 5 | 3mo ago | MIT | A | 77 | Claude Code, Codex |
| agent-spending-mandatemohitagw15856/pm-claude-skills | Skill | 1.5k | yesterday | MIT | A | 113 | Claude Code |
| saas-billingroedyrustam/vibes-plug | Skill | 121 | yesterday | MIT | A | 36 | Cursor |
| payment-gateway-expertroedyrustam/vibes-plug | Skill | 121 | yesterday | MIT | A | 34 | Cursor |
| marketplace-purchase-vettingAtlasOmnia/donna-starter | Skill | 138 | 11d ago | MIT | A | 72 | Claude Code, Codex |
| stripe-integrationfinsilabs/awesome-ecommerce-skills | Skill | 63 | 15d ago | MIT | A | 29 | Claude Code, Codex |
| doku-mcp-serverroedyrustam/vibes-plug | Skill | 121 | yesterday | MIT | B | 40 | Cursor |