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/stripe-projectsnpx skills add stripe/ai --skill stripe-projectsgit 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/stripe-projects)<a href="https://agentmods.dev/skills/stripe/ai/stripe-projects"><img src="https://agentmods.dev/badge/skills/stripe/ai/stripe-projects.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.00213 | $0.01838 |
| Opus 5 | $0.00106 | $0.00919 |
| Sonnet 5 | $0.00043 | $0.00368 |
| Haiku 4.5 | $0.00021 | $0.00184 |
Grade A, and why
stripe-projects 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- stripe-projects — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Projects — Service Provisioning
Provision third-party services (databases, auth, hosting, analytics, caching, AI, observability) and retrieve API keys/tokens using the Stripe Projects CLI plugin.
Workflow
Step 1: Ensure Stripe CLI + Projects Plugin
Check if the Stripe CLI is available:
which stripe && stripe --version
If not installed or below version 1.40.0:
- macOS (Homebrew):
brew install stripe/stripe-cli/stripe(orbrew upgrade stripe/stripe-cli/stripe) - Other platforms: Direct the user to https://docs.stripe.com/stripe-cli/install for up-to-date instructions.
Then ensure the Projects plugin is installed:
stripe plugin install projects
Step 2: Search the Catalog
Confirm the requested provider/service exists:
stripe projects search <query> --json
If result_count is 0, inform the user the service was not found and stop.
If the user’s request is vague (for example, “I need a database”), browse the catalog to suggest options:
stripe projects catalog --json
Step 3: Initialize a Project
Check if a project is already initialized:
stripe projects status --json
If not initialized, run a preflight check first to reveal all blockers at once:
stripe projects init --preflight --json
If all preflight checks pass, or the only failure is TOS_ACCEPTANCE_REQUIRED, proceed:
stripe projects init --accept-tos --yes
If any check fails with BROWSER_AUTH_REQUIRED, PROJECTS_SESSION_UNUSABLE, or ACCOUNT_NOT_ELIGIBLE, stop here. Report that check’s message and remedy to the user verbatim and let them resolve it — clearing these requires a browser sign-in or a Dashboard visit you cannot perform. Do not run stripe projects init yourself and do not re-run the preflight: neither clears the blocker for you, since only the user can complete a browser sign-in or a Dashboard step.
Follow the remedy the failing check prints rather than assuming stripe login is the fix. If a Stripe CLI session already exists, stripe login reports that you are already logged in and exits 0 without changing anything — an exit code of 0 from a login command does not mean the blocker cleared.
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 · 175 lines · 213 tokens per session scan A 117493ae0552
stripe-projects is a skill published in the GitHub repository stripe/ai (1,790 stars, last pushed yesterday), licensed MIT. It adds 213 tokens to every session and 1,838 once invoked, about $0.0011 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
database-migrations
Manage, generate, apply, and validate PostgreSQL schema migrations using SQLAlchemy and Alembic, including the pre-1.0 branch-baseline policy and targeted database verification.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
postgres-patterns
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on Supabase best practices.