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 agentmods add skills/dodopayments/dodo-agent-plugin/billing-sdknpx skills add dodopayments/dodo-agent-plugin --skill billing-sdkgit clone --depth 1 https://github.com/dodopayments/dodo-agent-pluginWrote 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/dodopayments/dodo-agent-plugin/billing-sdk)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/billing-sdk"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/billing-sdk.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 | $0.00041 | $0.04311 |
| Opus 5 | $0.00020 | $0.02155 |
| Sonnet 5 | $0.00008 | $0.00862 |
| Haiku 4.5 | $0.00004 | $0.00431 |
Grade A, and why
billing-sdk 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.
This is a copy
100% identical to billing-sdk — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 489 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BillingSDK
BillingSDK is an open-source React component library for billing interfaces, maintained by Dodo Payments
at github.com/dodopayments/billingsdk. Components are copied into your repository as source files
(shadcn/ui model) rather than imported from a runtime npm package.
Use this skill when building the front end. All Dodo Payments API calls belong in server-side route handlers; the components are presentation only.
When to use this skill
- Building a pricing page that starts a Dodo checkout.
- Building an account/billing page with subscription details and a "Manage billing" button.
- Rendering usage meters, credit balances, invoice history, or upcoming charges.
- Adding cancel / upgrade / downgrade UI to an existing React or Next.js app.
- Deciding whether to scaffold with
@billingsdk/cli initor add individual components.
Core concepts
Source-installed, not a dependency. The repository root package billingsdk is private. There is no
verified general-purpose runtime npm component package. You install components through the CLI or the
shadcn registry, and the .tsx files land in your project under components/billingsdk/.
The installed file is the prop contract. Because components are vendored into your repo, the exported
props type in components/billingsdk/<component>.tsx is authoritative for your version. Read it before
wiring callbacks. Do not assume prop names from another project.
The registry is the installability source of truth. Use
registry.json. The docs navigation
has drifted from it — for example payment-success-dialog appears in navigation but not in the current
registry. If add fails, the block is not in the registry.
Components never call Dodo. They receive data and fire callbacks. Every Dodo Payments call runs on your
server with DODO_PAYMENTS_API_KEY. That key is dodo_test_... or dodo_live_... and must never reach
the browser.
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 · 489 lines · 41 tokens per session scan A 34c8ea364412
billing-sdk is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 5d ago), licensed MIT. It adds 41 tokens to every session and 4,311 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to billing-sdk, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
opencode-ensemble
Use when coordinating multiple coding agents, delegating independent software work, managing OpenCode Ensemble teams, choosing teammate roles or models, reviewing teammate output, or deciding whether parallel execution is appropriate.
ahk-consultant
Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.
ce:plan
Create structured plans for any multi-step task -- software features, research workflows, events, study plans, or any goal that benefits from structured breakdown. Also deepen existing plans with interactive review of sub-agent findings. Use for plan creation when the user says 'plan this', 'create a plan', 'write a…
ce:review
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
ce:compound-refresh
Refresh stale or drifting learnings and pattern docs in docs/solutions/ by reviewing, updating, consolidating, replacing, or deleting them against the current codebase. Use after refactors, migrations, dependency upgrades, or when a retrieved learning feels outdated or wrong. Also use when reviewing docs/solutions/…
ce:compound
Document a recently solved problem to compound your team's knowledge.