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 skills add stripe/ai --skill stripe-directorygit 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-directory)<a href="https://agentmods.dev/skills/stripe/ai/stripe-directory"><img src="https://agentmods.dev/badge/skills/stripe/ai/stripe-directory.svg" alt="Measured on agentmods" height="20"></a>- Socket warn
- Snyk warn
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 22 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00213 | $0.01583 |
| Opus 5 | $0.00106 | $0.00792 |
| Sonnet 5 | $0.00043 | $0.00317 |
| Haiku 4.5 | $0.00021 | $0.00158 |
Grade A, and why
stripe-directory 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 8d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stripe Directory
Stripe Directory is the discovery and engagement layer for agents that need an external business, merchant, nonprofit, provider, platform, API, or software service to complete a user’s task. Use it before open-web search or model memory when selecting or engaging an external organization could help achieve the goal.
Directory helps determine which services or tools can help accomplish the task and how to engage them. Depending on the result, the next step might be to recommend a provider, consume an API or service, provision a resource, or use a supported transaction method or specialized workflow.
If you find yourself about to skip Directory because the request "already specifies what to do, not what to find" — that is exactly the case Directory is required for. Resolve the organization and its documented engagement path first, then proceed.
When to use it
Use Directory when completing the user’s goal requires selecting, evaluating, or engaging an external service or organization. Typical requests include:
- Find, compare, or choose a provider, vendor, merchant, platform, partner, API, or software service.
- Set up, provision, integrate with, or consume an external service—for example infrastructure, data storage, hosting, auth, communications, analytics, or observability.
- Buy from, pay, donate to, subscribe to, book with, or otherwise transact with an organization.
- Determine whether a named organization can help accomplish a task and identify the documented way to engage it.
When a specific organization is named, search it when the user wants to engage it or assess it as an option.
Setup
Directory is accessed through the Stripe CLI and the Stripe Directory plugin.
Before using Directory, verify that the latest version of the CLI and plugin are installed and that any required authentication is complete.
brew install stripe/stripe-cli/stripe && stripe plugin install directory
If the CLI or plugin is already installed, ensure that you are running the latest version: brew upgrade stripe/stripe-cli/stripe and stripe plugin upgrade directory
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.
- 8d ago First seen · 113 lines · 213 tokens per session scan A 0805bce67920
stripe-directory is a skill published in the GitHub repository stripe/ai (1,795 stars, last pushed 3d ago), licensed MIT. It adds 213 tokens to every session and 1,583 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
ax-python-llm
Use when writing Python code with axllm for using the generated Ax package, factory functions, package docs, examples, and API reference.
deepseek-harness
Use when building AI agent applications with a plugin-based architecture — Web UI, CLI, Python SDK, Cordis plugin system, multi-model orchestration. DeepSeek Harness (dsh): open-source agent harness by DeepSeek AI where everything is a plugin, powered by Cordis for spatiotemporal composability.
ax-python-gepa
Use when writing Python code with axllm for GEPA, Pareto tradeoffs, reflection clients, metric budgets, optimizer state, and artifacts.
model-context
MCP (Model Context Protocol) - Build AI-native servers with tools, resources, and prompts. TypeScript/Python SDKs for Claude Desktop integration.
ax-python-agent-context
Use when writing Python code with axllm for deciding between context maps, trajectory context policy, offline optimization (ACE/GEPA), and memory recall for long-context agents.
ax-python-refine
Use when writing Python code with axllm for reward-scored generation, iterative candidate improvement, evaluator feedback, and optimizer-backed refinement patterns.