Stripe AI is a collection of SDKs, tools, an MCP server, and agent skills for building AI products and businesses with Stripe's billing infrastructure. Developers use it to connect Stripe payments and metering to language models and agent frameworks, while the catalogue entries provide Stripe-specific skills, commands, plugins, and agent integrations.
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/stripe/ai/connect-recommendnpx skills add stripe/ai --skill connect-recommendgit clone --depth 1 https://github.com/stripe/aiWrote 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/stripe/ai/connect-recommend)<a href="https://agentmods.dev/skills/stripe/ai/connect-recommend"><img src="https://agentmods.dev/badge/skills/stripe/ai/connect-recommend.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 | $0.00151 | $0.04202 |
| Opus 5 | $0.00076 | $0.02101 |
| Sonnet 5 | $0.00030 | $0.00840 |
| Haiku 4.5 | $0.00015 | $0.00420 |
Grade A, and why
connect-recommend 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Connect recommend
Recommend the right Stripe Connect integration configuration. The user only needs to provide a company URL or describe their business — the skill figures out the rest.
Interaction model
User must confirm interactions. Every decision point in this skill MUST be confirmed with the user with clear, numbered options and short descriptions. One question at a time — never overwhelm the user.
Auto-act on low-cost actions. Never ask permission for:
- Generating the markdown recommendation plan — just generate it
- Scanning the codebase — just scan it
- Reading reference files — just read them
Never end with passive text. Every stopping point must end with a prompt to the user offering concrete next actions.
Terminology rules (user-facing output)
Before generating any user-facing output, read <references/terminology-rules.md>. Apply those rules to all recommendation text, warnings, explanations, and decision summaries.
Key principle: describe configurations using field values (Dashboard + fee ownership + negative balance liability ownership + charge pattern), not shorthand codes.
Output Brevity
Keep responses concise. The user is making decisions, not reading documentation.
- Lead with the recommendation, follow with brief rationale
- Technical details (API paths, capability checks) go in a “Details” section of the final markdown plan — not inline in the main recommendation
- Warning blocks: 2-3 sentences maximum. State the issue and the fix. No mechanism deep-dives unless the user asks.
- Decision summary: bullet points only, one line per decision
- Never output more than ~40 lines in a single response during interactive mode
Only mention out-of-scope limitations when they’re directly relevant to what the user asked about. Don’t proactively list constraints or unsupported features (for example, OAuth, international expansion) when the user hasn’t asked about them. “Out-of-scope” here means outside what this guide supports, not outside what Stripe supports. Research these topics in the Stripe public documentation (docs.stripe.com) rather than saying they’re out-of-scope.
What ships with it
8 files beside SKILL.md 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.
- references/account-types.md 15 KB
- references/charge-patterns.md 11 KB
- references/company-researcher.md 7.6 KB
- references/compatibility-matrix.md 16 KB
- references/decision-matrix.md 34 KB
- references/discovery-questions.md 16 KB
- references/recommendation-template.md 14 KB
- references/terminology-rules.md 6.5 KB
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.
- 5d ago First seen · 358 lines · 151 tokens per session scan A 84dc5a2622ca
connect-recommend is a skill published in the GitHub repository stripe/ai (1,790 stars, last pushed yesterday), licensed MIT. It adds 151 tokens to every session and 4,202 once invoked, about $0.0008 per session on Opus 5. 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-08-30.
Other skills, from other repositories
x402
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing…
bump-mthds
Move this repo's exact mthds dependency pin to the latest release on PyPI (or a version you name), re-lock, adapt the engine source to whatever the new release broke, run the checks, and write the CHANGELOG entry — stopping before the commit. Use whenever the user says "bump mthds", "update mthds", "upgrade mthds"…
bump-kajson
Move this repo's exact kajson dependency pin to the latest release on PyPI (or a version you name), re-lock, adapt the engine to whatever the new release changed, retire any workaround the release makes unnecessary, run the checks, and write the CHANGELOG entry — stopping before the commit. Use whenever the user says…
billing-stripe
Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.
reviewing-personhog-protocol
The full review process for personhog coordination-protocol changes — leases, fencing, handoffs, supervisors, failure budgets, warming, and changelog semantics. Use before pushing or requesting review on any personhog protocol changeset, when asked for an exhaustive or careful review of personhog code, and after any…
modeling-revenue-metrics
Build reusable revenue models — MRR, ARR, gross revenue, new/expansion/contraction/churn, ARPU, LTV, and per-customer/per-account revenue — on either PostHog data-warehouse views (HogQL) or an external dbt project. Use when the user wants to model, define, or compute recurring revenue, monthly/annual recurring…