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 Ckokoski/AuthorAgent --skill error-recoverygit clone --depth 1 https://github.com/Ckokoski/AuthorAgentWrote 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/ckokoski/authoragent/error-recovery)<a href="https://agentmods.dev/skills/ckokoski/authoragent/error-recovery"><img src="https://agentmods.dev/badge/skills/ckokoski/authoragent/error-recovery.svg" alt="Measured on agentmods" 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.00018 | $0.01631 |
| Opus 5 | $0.00009 | $0.00816 |
| Sonnet 5 | $0.00004 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
error-recovery 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 7d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Recovery — Core Skill
When things go wrong, AuthorAgent doesn't just report the error — it diagnoses the root cause, attempts automatic recovery, and remembers the fix for next time.
Error Categories
1. AI Provider Errors
Symptoms: API timeouts, rate limits, auth failures, model unavailability
Error Detected: Gemini API returned 429 (rate limited)
Diagnosis: Too many requests in short period (>60/min)
Recovery Strategy:
1. ✅ Wait 30 seconds and retry (attempt 1 of 3)
2. ⏳ Switch to DeepSeek as fallback provider
3. ⏳ If all providers fail, queue the task for later
Lesson Stored: "Gemini rate limits at ~60 req/min.
Add 500ms delay between batch requests."
Recovery Playbook:
- 429 Rate Limited → Wait + retry → Switch provider → Queue
- 401 Unauthorized → Check API key in vault → Alert user if missing
- 503 Service Unavailable → Retry with backoff → Switch provider
- Timeout → Reduce prompt length → Retry → Switch provider
- Content filtered → Rephrase prompt → Retry without triggering content filter
- Context too long → Truncate prior results → Summarize context → Retry
2. Goal Execution Errors
Symptoms: Step failures, invalid AI output, parsing failures
Error Detected: Goal step "Create character profiles" failed
AI returned unstructured text instead of character profiles
Diagnosis: Prompt was too open-ended for structured output
Recovery Strategy:
1. ✅ Reformulate prompt with explicit structure requirements
2. ✅ Add output format example to prompt
3. ✅ Retry with reformulated prompt
New prompt: "Create character profiles in this exact format:
NAME: [name]
AGE: [age]
ROLE: [protagonist/antagonist/supporting]
..."
Result: ✅ Step succeeded on retry
Recovery Playbook:
- Unstructured output → Add format constraints → Retry
- JSON parse error → Strip markdown fences → Extract JSON → Retry with stricter prompt
- Output too short → Request longer output → Increase max tokens → Retry
- Repeated failure → Skip step → Flag for user review → Continue goal
- Nonsensical output → Switch provider → Reduce temperature → Retry
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.
- 7d ago First seen · 213 lines · 18 tokens per session scan A cbb370c15d97
error-recovery is a skill published in the GitHub repository Ckokoski/AuthorAgent (103 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 1,631 once invoked, about $0.0001 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
browserwing-admin
Manage and operate BrowserWing — an intelligent browser automation platform. Install dependencies, configure LLM, create/manage/execute automation scripts, use AI-driven exploration to generate scripts, browse the script marketplace, and troubleshoot issues.
error-experience-library
An error knowledge base that stores recurring error patterns, their causes, and the fixes that worked. It can search past entries and track whether each suggested fix succeeded.
mindos
MindOS: local knowledge assistant & shared KB. Keeps decisions, notes, SOPs, debugging lessons, research findings, preferences across sessions/agents. Core: save notes, search KB, organize files, run workflows, review, append CSV, hand off context, distill lessons. NOT for app source or paths outside KB. Triggers…
sivtr-memory
Retrieve shared local work memory: terminal activity, AI conversation history, prior decisions, validation evidence, debugging trails, recaps, and handoff context. Use before asking the user to repeat local work context.
memory-safety-c-cpp
Reference vocabulary for memory-safety vulnerabilities in native C/C++ code — bug-class taxonomy, common arithmetic patterns that lead to corruption, dispatch-family discipline, type-confusion idioms, use-after-free patterns, and exploitability factors. Read when analyzing, hypothesizing, designing harnesses for, or…
doris-debug-resource-isolation
Use for Doris Workload Group / resource tag queue starvation, CPU/memory isolation leaks, and workload policy debugging. Commands: SHOW WORKLOAD GROUPS, EXPLAIN resource.