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.
git clone --depth 1 https://github.com/acaprino/daodanWrote 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/acaprino/daodan/stripe)<a href="https://agentmods.dev/plugins/acaprino/daodan/stripe"><img src="https://agentmods.dev/badge/plugins/acaprino/daodan/stripe/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/plugins/acaprino/daodan/stripe"><img src="https://agentmods.dev/badge/plugins/acaprino/daodan/stripe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stripe 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 16d 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.
What it actually says
{
"author": {
"name": "Alfio Caprino"
},
"description": "Stripe payments, subscriptions, Connect marketplaces, and revenue optimization for SaaS monetization; includes a dedicated skill (link-first references + scripts) for API patterns, Next.js/TypeScript integration, Embedded Checkout, Billing Meters, Entitlements, webhook reliability and auditing, Stripe Agent Toolkit for LLM tool-calling, test-clock simulation, PCI DSS 4.0 compliance, and pricing design",
"license": "MIT",
"name": "stripe",
"version": "2.6.0"
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 3 agents travel with it, and installing the plugin installs all of them — 367 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 16d ago Changed 35841366a112
- 1mo ago First seen · 10 lines scan A 8c938380fa64
stripe is a plugin published in the GitHub repository acaprino/daodan (9 stars, last pushed today), 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-05.
Other plugins, from other repositories
polar-skills
Official Polar skills for billing, subscriptions, and local development.
stripe-skills
Official Stripe skills for payments, billing, Connect, Apps, and API upgrades.
paypal
PayPal development plugin for Claude — integrate payments, subscriptions, invoices, disputes, and more using PayPal's APIs and MCP server.
snaplii-a2m-payment
Agent-to-Merchant payments — AI agents complete gift card transactions without checkout across 500+ brands via Snaplii.
tododeia marketplace
Payment integration tooling for Claude Code, from tododeia. Local-first plugins that write production payment code and block the insecure patterns as they are written.
scvd-general-store
Evidence observatory: x402/MPP inspection, signed receipt checks and settlement attestations.