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/checkout-integrationnpx skills add dodopayments/dodo-agent-plugin --skill checkout-integrationgit 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/checkout-integration)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/checkout-integration"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/checkout-integration.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.1 | $0.00037 | $0.05801 |
| Opus 5 | $0.00018 | $0.02900 |
| Sonnet 5 | $0.00007 | $0.01160 |
| Haiku 4.5 | $0.00004 | $0.00580 |
Grade A, and why
checkout-integration 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 6d 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 checkout-integration — 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 — 851 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dodo Payments Checkout Integration
Use client.checkoutSessions.create(...) to build hosted checkout pages or overlay checkout modals. This is the recommended path for all new payment integrations.
When to use this skill
- Build a one-time payment checkout flow
- Create a subscription checkout with optional trial
- Embed checkout in an overlay or inline modal
- Collect customer billing info and custom fields at checkout
- Apply discount codes or handle currency selection
- Redirect customers after payment completes
Checkout Methods
Dodo Payments offers three ways to collect payment:
| Method | Best For | Setup |
|---|---|---|
| Checkout Sessions (recommended) | Most integrations; full control | Server-side SDK call |
| Static Payment Links | No-code sharing; reusable URLs | Dashboard or direct URL |
| Overlay/Inline Checkout | Checkout stays on your site | Client-side SDK |
Legacy: Dynamic Payment Links created via POST /payments or POST /subscriptions are deprecated. Use Checkout Sessions instead.
Core Concepts
Amounts in smallest currency unit: All prices are in cents (or equivalent). A $10 USD charge is 1000.
Checkout Session: A single-use session that generates a hosted checkout URL. Expires after 24 hours (or 15 minutes if confirm=true).
Return URL: Where the customer lands after payment. Query parameters include status=success and session_id.
Entitlement on webhook: The browser redirect is not the source of truth. Always verify payment via webhook before granting access. See webhook-integration skill for verification.
Create a Checkout Session
Basic One-Time Payment
import DodoPayments from 'dodopayments';
const client = new DodoPayments({
bearerToken: process.env.DODO_PAYMENTS_API_KEY,
environment: 'test_mode', // or 'live_mode'
});
const session = await client.checkoutSessions.create({
product_cart: [
{ product_id: 'pdt_example', quantity: 1 }
],
customer: {
email: '[email protected]',
name: 'Jane Doe'
},
return_url: 'https://yoursite.com/checkout/success'
});
console.log('Redirect to:', session.checkout_url);
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.
- 6d ago First seen · 851 lines · 37 tokens per session scan A 9eb3cd448204
checkout-integration is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 5,801 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 checkout-integration, 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.