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.
/plugin marketplace add dodopayments/skillsnpx agentmods add plugins/dodopayments/skills/dodo-best-practicesgit clone --depth 1 https://github.com/dodopayments/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/plugins/dodopayments/skills/dodo-best-practices)<a href="https://agentmods.dev/plugins/dodopayments/skills/dodo-best-practices"><img src="https://agentmods.dev/badge/plugins/dodopayments/skills/dodo-best-practices.svg" alt="Measured on agentmods" height="20"></a>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 today.
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
{
"name": "dodo-best-practices",
"description": "Guide for initial Dodo Payments setup, including SDK installation, test and live environments, API keys, and the canonical checkout-to-webhook architecture.",
"source": "./",
"strict": false,
"skills": [
"./dodo-payments/dodo-best-practices"
]
}What ships with it
1 file beside marketplace.json#dodo-best-practices in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 9 lines scan A 7179a28c1457
dodo-best-practices is a plugin published in the GitHub repository dodopayments/skills (12 stars, last pushed 26d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
newebpay
藍新金流(NewebPay)完整串接工具 - 支付串接、交易查詢、退款.
payment-help
台灣金流服務比較與推薦 - 幫助選擇最適合的支付方案.
ecpay
綠界科技(ECPay)串接指南 - 全方位金流、電子發票.
payuni
統一金流(PAYUNi)完整串接工具 - 支付串接、交易查詢、Webhook 處理.
shipshitdev-payments
Payment processing and financial integrations.
stripe-implementer
Implement Stripe payment processing, subscription management, webhook handling, and customer management in Next.js and NestJS applications. Use when integrating Stripe payments, subscription billing, webhooks, customer management, or checkout and payment intents.