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 jezweb/vite-flare-starter --skill enrich-errorgit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/jezweb/vite-flare-starter/enrich-error)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/enrich-error"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/enrich-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/jezweb/vite-flare-starter/enrich-error"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/enrich-error.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00044 | $0.00589 |
| Opus 5 | $0.00022 | $0.00295 |
| Sonnet 5 | $0.00009 | $0.00118 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
enrich-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 10d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enrich Error
Purpose
Raw error messages are useless to non-developer users. Error: fetch failed (status 401) doesn't tell anyone what to do.
This skill rewrites errors into findings with three properties:
- What happened — in plain English, no jargon.
- Why — the underlying cause if you can guess.
- What to do — the specific next step (link if possible).
Pattern
For each error, produce an inbox_add payload like:
{
"kind": "routine_error",
"summary": "<plain English what + actionable next step>",
"importance": "medium",
"reasoning": "<technical detail for debugging>",
"suggestedAction": { "label": "<verb-led link text>", "link": "<dashboard path>" }
}
Common error patterns + rewrites
| Raw error | Plain summary | Suggested action |
|---|---|---|
401 Unauthorized from Gmail |
"Gmail connection expired" | Reconnect at /dashboard/connectors |
403 Forbidden from Slack |
"Slack token doesn't have the scope this routine needs" | Re-authorise in Connectors |
429 Too Many Requests |
"Hit rate limit on <service>" | (no action — auto-retries) |
5xx from any service |
"<service> is down or having issues" | (no action — wait it out) |
corrupt or unsupported data |
"Couldn't process the file" | Check the source file format |
BudgetExceededError |
"Daily budget cap reached for this routine" | Raise the cap on the routine detail page |
| Network timeout | "Connection timed out reaching <service>" | (no action — auto-retries) |
Severity rules
- high: auth/connector failures (user MUST act for the routine to keep working)
- medium: transient errors that have happened ≥3 fires in a row
- low: one-off transient errors (rate limits, timeouts) — log it but don't pester
When NOT to enrich
If the error is a programming bug (TypeError, ReferenceError, schema mismatch), produce a short routine_error finding tagged for the developer rather than the user, with the raw stack in reasoning. The user can't fix code; the dev can.
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.
- 10d ago First seen · 56 lines · 0 tokens per session scan A 4d39164c2834
enrich-error is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 589 once invoked, about $0.0002 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 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.