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 dodopayments/dodo-agent-plugin --skill dodo-best-practicesgit 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/dodo-best-practices)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/dodo-best-practices"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/dodo-best-practices/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/dodopayments/dodo-agent-plugin/dodo-best-practices"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/dodo-best-practices.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.00036 | $0.03356 |
| Opus 5 | $0.00018 | $0.01678 |
| Sonnet 5 | $0.00007 | $0.00671 |
| Haiku 4.5 | $0.00004 | $0.00336 |
Grade A, and why
dodo-best-practices 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 8d 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 dodo-best-practices — 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 — 472 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dodo Payments Integration Guide
This skill covers the foundational concepts and setup for Dodo Payments. Use it when starting a new integration, setting up the SDK, or understanding the core payment flow.
When to use this skill
- You're building a new payment integration and need to understand Dodo's architecture
- You need to install and initialize the SDK in your language
- You want to understand the canonical payment flow and webhook verification
- You're choosing between framework adapters or payment methods
- You need to know what Dodo handles versus what you must build
What is Dodo Payments
Dodo Payments is a Merchant of Record (MoR). That means Dodo is the legal seller on every transaction, handles sales tax registration and calculation across all jurisdictions, remits taxes to authorities, and manages card-network disputes and chargebacks. As a developer, you don't build a sales-tax engine or dispute-handling system. You create checkout sessions, listen to webhooks, and grant access when payment succeeds.
Environment Setup
Base URLs
Only two real base URLs exist:
- Live:
https://live.dodopayments.com - Test:
https://test.dodopayments.com
Never use api.dodopayments.com — it has no DNS record and cannot be reached.
API Keys
Keys have two formats:
- Test:
dodo_test_... - Live:
dodo_live_...
Environment Variables
DODO_PAYMENTS_API_KEY # Bearer token for API requests
DODO_PAYMENTS_WEBHOOK_KEY # Secret for webhook signature verification
Default Environment
The environment parameter defaults to live_mode if omitted. Always pass test_mode explicitly during development.
SDK Installation & Initialization
TypeScript/Node.js
npm install dodopayments
import DodoPayments from 'dodopayments';
const client = new DodoPayments({
bearerToken: process.env.DODO_PAYMENTS_API_KEY,
environment: 'test_mode', // defaults to 'live_mode'
});
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.
- 8d ago First seen · 472 lines · 36 tokens per session scan A b813ae0918b4
dodo-best-practices is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 3,356 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 dodo-best-practices, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
stripe-billing-subscriptions
Analyze Stripe customers, subscriptions, prices, invoices, payment status, and lifecycle transitions with explicit environment and object scope.
checkout-integration
Guide for starting hosted Checkout Sessions, payment links, and overlay or inline checkout for one-time and recurring products; use subscription-integration for post-checkout lifecycle management.
refunds-and-disputes
Guide for issuing refunds, handling disputes and chargebacks, and reconciling customer access with Dodo Payments.
stripe-best-practices
Guide Stripe integration decisions — API choice, Connect, billing, Treasury, key/webhook security. Use when building, modifying, or reviewing any Stripe payment, marketplace, or subscription.
payments
This skill should be used when adding payments, subscriptions, billing, or pricing to a SaaS — Stripe integration, checkout, plans, the customer portal, webhooks, or deciding a pricing model. Trigger phrases include "add Stripe", "accept payments", "add a subscription", "charge users", "pricing tiers", "checkout"…
pn-payment-integration
Stripe, PayPal, Square integration. Checkout, subscriptions, webhooks, PCI compliance. Use when implementing payments, billing, or subscription features.