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/secondsky/claude-skillsWrote 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/secondsky/claude-skills/explain-error)<a href="https://agentmods.dev/commands/secondsky/claude-skills/explain-error"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/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/secondsky/claude-skills/explain-error"><img src="https://agentmods.dev/badge/commands/secondsky/claude-skills/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.00011 | $0.00649 |
| Opus 5.5 | $0.00004 | $0.00260 |
| Sonnet 5.5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explain Better Auth Error
Provide a comprehensive explanation of the given Better Auth error code or error message.
Process
- Accept the error from arguments (error code or full error message)
- Check error catalog first:
- Load
references/error-catalog.mdto see if this is one of the 15 documented errors - If found, use catalog as primary reference
- Load
- Explain in plain English what the error means
- List common causes specific to the error
- Provide solutions:
- Configuration fixes
- Code corrections
- Cloudflare D1-specific solutions (if applicable)
- Generate error handling code showing:
- How to catch this specific error
- User-friendly error messages
- Whether retry is appropriate
- TypeScript type guards if applicable
- Mention related errors the developer should be aware of
- Link to documentation:
- Better Auth docs: https://better-auth.com/docs
- Error catalog reference file (if documented)
Common Better Auth Errors
If no specific error provided, list top 5 most common errors:
- d1Adapter is not exported - Use drizzleAdapter instead
- Schema generation fails - Use Drizzle Kit, not better-auth migrate
- CamelCase vs snake_case mismatch - Column naming issues
- CORS errors - Missing credentials or origin configuration
- OAuth redirect URI mismatch - Callback URL configuration
Error Categories
Database Errors:
- D1 adapter issues
- Schema migration problems
- Connection failures
Authentication Errors:
- Session validation failures
- Token expiration
- Invalid credentials
OAuth Errors:
- Provider configuration
- Redirect URI mismatches
- Scope issues
CORS/Security Errors:
- Origin blocking
- Cookie not sent
- CSRF token mismatch
Example Usage
User: /better-auth:explain-error "SESSION_NOT_FOUND"
Response:
Error: SESSION_NOT_FOUND
What it means:
The session token provided is not found in the database or has expired.
Common causes:
1. Session expired (default: 7 days)
2. Session manually deleted
3. Database connection issue
4. Cookie not sent with request
Solutions:
[Detailed solutions with code examples]
Error handling code:
[Production-ready code example]
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 · 103 lines · 11 tokens per session scan A 8a07f7a52ec1
explain-error is a command published in the GitHub repository secondsky/claude-skills (231 stars, last pushed 19d ago), licensed MIT. It adds 11 tokens to every session and 649 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
correlate
Find related failures through pattern matching.
diff
Compare two command outputs with intelligent diff.
doctor
Run FewWord self-diagnostics to check health and fix common issues.
open
Open/retrieve an offloaded output by ID or shortcut.
help
Explain FewWord plugin, how it works, and available commands.
search
Search through offloaded outputs with hard caps.