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 smicolon/ai-kit --skill explain-errorgit clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/smicolon/ai-kit/explain-error)<a href="https://agentmods.dev/skills/smicolon/ai-kit/explain-error"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/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/skills/smicolon/ai-kit/explain-error"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/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.00029 | $0.00863 |
| Opus 5.5 | $0.00012 | $0.00345 |
| Sonnet 5.5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Better Auth Error Diagnostician & Explainer
This skill diagnoses and provides actionable resolutions for common Better Auth runtime errors, client error codes, configuration pitfalls, and database adapter issues.
Common Error Codes & Resolutions
1. INVALID_EMAIL_OR_PASSWORD
- Cause: User credentials do not match database records, or password hashing mismatch.
- Resolution:
- Verify that password hashing algorithm has not changed between migrations.
- Verify that input email is trimmed/lowercased if
emailAndPassword.autoSignInor normalization is enabled. - Check client-side error handling:
const { data, error } = await authClient.signIn.email({ email, password, }) if (error?.status === 401 || error?.code === 'INVALID_EMAIL_OR_PASSWORD') { // Prompt user with user-friendly message }
2. USER_ALREADY_EXISTS
- Cause: Attempting to sign up with an email or account ID already in use.
- Resolution:
- Direct user to sign in or password reset flow.
- If social login is used with existing email, check
accountLinking.enabled:export const auth = betterAuth({ account: { accountLinking: { enabled: true, trustedProviders: ['google', 'github'], }, }, })
3. SESSION_EXPIRED / UNAUTHORIZED
- Cause: Cookie expired, missing
credentials: "include"on cross-origin fetch, or cookie domain mismatch. - Resolution:
- Client side: ensure
authClienthas the exactbaseURLmatching server. - Cross-domain setup:
export const auth = betterAuth({ trustedOrigins: ['https://app.example.com', 'http://localhost:3000'], advanced: { crossSubDomainCookies: { enabled: true, domain: '.example.com', }, }, })
- Client side: ensure
4. FAILED_TO_VERIFY_EMAIL / INVALID_TOKEN
- Cause: Verification token expired or used already.
- Resolution:
- Verify email verification URL configuration in
emailVerification:emailVerification: { sendOnSignUp: true, autoSignInAfterVerification: true, sendVerificationEmail: async ({ user, url, token }) => { await sendEmail({ to: user.email, url }) }, }
- Verify email verification URL configuration in
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 · 99 lines · 29 tokens per session scan A 2fb12603f46d
explain-error is a skill published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 863 once invoked, about $0.0001 per session on Opus 5.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-09-04.
Other skills, from other repositories
error-recovery-patterns
What to do when things break.
perf-optimizer
Profile and optimize application performance — algorithmic complexity, caching strategies, database queries, and bundle size.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
convex-performance-audit
Audits Convex performance for reads, subscriptions, write contention, and function limits. Use for slow features, insights findings, OCC conflicts, or read amplification.
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.