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 commands/stripe/ai/explain-errorgit clone --depth 1 https://github.com/stripe/aiWhat 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.00010 | $0.00158 |
| Opus 5 | $0.00005 | $0.00079 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
explain-error 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 yesterday.
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:
- explain-error — 100% identical, 0 lines differ
What it actually says
Explain Stripe Error
Provide a comprehensive explanation of the given Stripe error code or error message:
- Accept the error code or full error message from the arguments
- Explain in plain English what the error means
- List common causes of this error
- Provide specific solutions and handling recommendations
- Generate error handling code in the project's language showing:
- How to catch this specific error
- User-friendly error messages
- Whether retry is appropriate
- Mention related error codes the developer should be aware of
- Include a link to the relevant Stripe documentation
Focus on actionable solutions and production-ready error handling patterns.
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.
- yesterday First seen · 21 lines · 10 tokens per session scan A 4d1e56c4de18
explain-error is a command published in the GitHub repository stripe/ai (1,783 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 158 once invoked, about $0.0001 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 commands, from other repositories
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
language
Command "language" from ErisPulse/ErisPulse, covering erispulse.cli.commands.language 模块, 模块概述, 类列表 and class languagecommand(command).
run-engine-tests
Fast local test loop for the engine package.
tech-debt
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create actionable remediation plans.