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 sourav15mukherjee/skillforge-free-skills --skill error-explainergit clone --depth 1 https://github.com/sourav15mukherjee/skillforge-free-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/skills/sourav15mukherjee/skillforge-free-skills/error-explainer)<a href="https://agentmods.dev/skills/sourav15mukherjee/skillforge-free-skills/error-explainer"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/error-explainer/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/sourav15mukherjee/skillforge-free-skills/error-explainer"><img src="https://agentmods.dev/badge/skills/sourav15mukherjee/skillforge-free-skills/error-explainer.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.00052 | $0.00758 |
| Opus 5 | $0.00026 | $0.00379 |
| Sonnet 5 | $0.00010 | $0.00152 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
error-explainer 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 9d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Explainer
Diagnose any error message and provide a clear explanation with a working fix.
Workflow
-
Parse the error Extract from the error message:
- Error type/name (TypeError, SyntaxError, ENOENT, etc.)
- Error message text
- File path and line number (if in stack trace)
- Framework context (React, Next.js, Node, webpack, etc.)
-
Read the source If a file and line number are referenced, read 20 lines of context around the error location.
-
Identify root cause Common patterns:
Cannot read properties of undefined→ trace the variable back to where it becomes undefinedModule not found→ check import paths, package.json, tsconfig pathsHydration mismatch→ find server/client rendering differencesENOENT→ verify the expected file path exists- Type errors → check type definitions and function signatures
-
Search for related patterns
# Find similar usage that works correctly grep -rn "theFunction\|theVariable" --include="*.ts" --include="*.tsx" -l -
Explain in plain English Structure the response:
What happened: One-sentence summary anyone can understand.
Why it happened: The specific chain of events that caused this error.
The fix: Exact code change with before/after.
Prevention: How to avoid this in the future (type guard, null check, etc.)
-
Apply the fix If the user confirms, edit the file directly. If multiple possible fixes exist, present options.
Rules
- Always read the actual source file before suggesting a fix — never guess
- Explain errors in plain language, not jargon
- If you can't determine the exact cause from the error alone, ask the user for the file content or to reproduce it
- For build errors, check package.json and config files first
- For type errors, check tsconfig.json and type definitions
- Never suggest
anyas a TypeScript fix — find the real type - If the error is from a dependency, check if the version matches the docs
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 92 lines · 52 tokens per session scan A 513b4ffd7370
error-explainer is a skill published in the GitHub repository sourav15mukherjee/skillforge-free-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 758 once invoked, about $0.0003 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.