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 refunds-and-disputesgit 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/refunds-and-disputes)<a href="https://agentmods.dev/skills/dodopayments/dodo-agent-plugin/refunds-and-disputes"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/refunds-and-disputes/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/refunds-and-disputes"><img src="https://agentmods.dev/badge/skills/dodopayments/dodo-agent-plugin/refunds-and-disputes.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.00028 | $0.02909 |
| Opus 5 | $0.00014 | $0.01455 |
| Sonnet 5 | $0.00006 | $0.00582 |
| Haiku 4.5 | $0.00003 | $0.00291 |
Grade A, and why
refunds-and-disputes 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 12d 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 refunds-and-disputes — 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 — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refunds and Disputes
This skill covers issuing refunds (full and partial), handling the dispute lifecycle, and managing customer access during payment reversals. Disputes are inbound-only; Dodo handles the card-network process as Merchant of Record while you control application access and evidence gathering.
When to use this skill
- You need to issue a refund (full or partial) for a payment
- A customer disputes a charge and you need to respond with evidence
- You're building access-revocation logic tied to refund or dispute status
- You need to reconcile customer entitlements after a payment reversal
- You're handling refund or dispute webhooks in production
Core concepts
Refunds are initiated by you via the API. Each refund has a status that tells you whether the money has actually left your account. Partial refunds target specific line items in the original payment.
Disputes are initiated by the customer's card network. You cannot create them; you only list and retrieve them. The dispute lifecycle spans seven events, each requiring different application actions.
Amounts are always in the smallest currency unit (cents for USD, paise for INR, etc.).
Access revocation means removing the customer's ability to use the product or service. On a dispute, you typically revoke access while it's open. Restore it only on dispute.won; all other outcomes keep access revoked until you reconcile them separately.
Refunds
Create a refund
import DodoPayments from 'dodopayments';
const client = new DodoPayments({
bearerToken: process.env.DODO_PAYMENTS_API_KEY,
environment: 'test_mode',
});
// Full refund
const refund = await client.refunds.create({
payment_id: 'pay_abc123',
});
console.log(refund.refund_id);
console.log(refund.status); // 'pending', 'succeeded', 'review', or 'failed'
Partial refund by item
To refund only specific items from a payment, pass the items array with each item ID and the amount to refund in the smallest currency unit. Omit amount to refund the whole item:
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.
- 12d ago First seen · 334 lines · 28 tokens per session scan A 83711d64c78c
refunds-and-disputes is a skill published in the GitHub repository dodopayments/dodo-agent-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 2,909 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to refunds-and-disputes, 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.