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/xiaoyuge886/aigcWrote 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/commands/xiaoyuge886/aigc/explain-error)<a href="https://agentmods.dev/commands/xiaoyuge886/aigc/explain-error"><img src="https://agentmods.dev/badge/commands/xiaoyuge886/aigc/explain-error/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/commands/xiaoyuge886/aigc/explain-error"><img src="https://agentmods.dev/badge/commands/xiaoyuge886/aigc/explain-error.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.00158 |
| Opus 5.5 | $0.00004 | $0.00063 |
| Sonnet 5.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 1mo 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.
This is a copy
100% identical to explain-error — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago First seen · 21 lines · 10 tokens per session scan A 4d1e56c4de18
explain-error is a command published in the GitHub repository xiaoyuge886/aigc (200 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 158 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to explain-error, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
debug-model
Debug and audit a financial model for errors.
sap-korean-tax-invoice-debug
A Korean-language troubleshooting command for electronic tax invoices, which are digital business invoices reported through Korea's tax systems, across SAP and several invoice providers.
sap-payment-run-debug
A guided troubleshooting process for failed F110 payment runs in SAP, where F110 creates scheduled payments to vendors.
brain-repair
Diagnose failed BRAIN alpha results and propose a repair batch.
debug-model
Debug and audit a financial model for errors.
gsd:debug
Systematic debugging with persistent state across context resets.