error-recovery-patterns

error-recovery-patterns is a skill for Claude Code, Codex from fabioc-aloha/Alex_Skill_Mall. It costs 13 tokens per session (1,279 once invoked), scanned A, original, MIT.

A collection of patterns for handling failures in software, from detecting and containing errors to retrying, falling back, recovering, and learning from them. It includes guidance for timeouts, rate limits, rollbacks, and distributed operations.

In plain words
What is it for?
Use it to design retry logic, fallback behavior, circuit breakers, rollback plans, database transactions, and compensating steps.
Why use it?
It helps systems respond predictably when networks, services, or business operations fail instead of repeatedly making the problem worse.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to design retry logic, fallback behavior, circuit breakers, rollback plans, database transactions, and compensating steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns
Install

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.

Any agent
npx skills add fabioc-aloha/Alex_Skill_Mall --skill error-recovery-patterns
Clone the repo
git clone --depth 1 https://github.com/fabioc-aloha/Alex_Skill_Mall

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for error-recovery-patterns

README.md
[![agentmods](https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns/github.svg)](https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns)
Your own site
<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns/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.

agentmods 80×15 button for error-recovery-patterns

Your own site · 80×15
<a href="https://agentmods.dev/skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns"><img src="https://agentmods.dev/badge/skills/fabioc-aloha/alex_skill_mall/error-recovery-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,279 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00013 $0.01279
Opus 5 $0.00006 $0.00639
Sonnet 5 $0.00003 $0.00256
Haiku 4.5 $0.00001 $0.00128

Measured 6d ago against content hash e7cbdd0c65b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

error-recovery-patterns scanned grade A with 1 finding 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 6d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

const response = await fetch(url, {
plugins/devops-process/error-recovery-patterns/skills/error-recovery-patterns/SKILL.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error Recovery Patterns Skill

What to do when things break.

Recovery Hierarchy

Prevent → Detect → Contain → Recover → Learn

Retry Rules

Retry Don't Retry
Network timeouts Validation errors (400)
Rate limits (429) Auth failures (401, 403)
Server errors (5xx) Not found (404)
Connection refused Business logic errors

Retry with Backoff

const delay = baseDelay * Math.pow(2, attempt - 1);
const jitter = Math.random() * 0.3 * delay;
await sleep(delay + jitter);

Circuit Breaker States

CLOSED → (failures > threshold) → OPEN → (timeout) → HALF-OPEN → (success) → CLOSED

Fallback Patterns

Pattern Use Case
Default value Config loading
Cached value Data fetch failure
Degraded service Non-critical features
const result = await primary().catch(() => fallback());

Rollback Patterns

Pattern Use Case
DB transaction Atomic operations
Saga (compensate) Distributed transactions
Feature flag Instant rollback

Saga Pattern Implementation

// Compensating transactions for distributed operations
interface SagaStep<T> {
  execute: () => Promise<T>;
  compensate: () => Promise<void>;
}

async function executeSaga<T>(steps: SagaStep<T>[]): Promise<T[]> {
  const completed: SagaStep<T>[] = [];
  const results: T[] = [];
  
  try {
    for (const step of steps) {
      results.push(await step.execute());
      completed.push(step);
    }
    return results;
  } catch (error) {
    // Compensate in reverse order
    for (const step of completed.reverse()) {
      try {
        await step.compensate();
      } catch (compensateError) {
        console.error('Compensation failed:', compensateError);
        // Log but continue compensating other steps
      }
    }
    throw error;
  }
}

// Usage: Order processing saga
const orderSaga: SagaStep<void>[] = [
  {
    execute: () => reserveInventory(orderId),
    compensate: () => releaseInventory(orderId)
  },
  {
    execute: () => chargePayment(orderId),
    compensate: () => refundPayment(orderId)
  },
  {
    execute: () => scheduleShipment(orderId),
    compensate: () => cancelShipment(orderId)
  }
];

Read the full file on GitHub · 211 lines

Changes

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.

  1. 6d ago First seen · 211 lines · 13 tokens per session scan A e7cbdd0c65b9

Subscribe to this mod's changes

error-recovery-patterns is a skill published in the GitHub repository fabioc-aloha/Alex_Skill_Mall (4 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 1,279 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

azure-messaging

Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue…

jonathan-vella/apex-accelerator · 135 tokens

apply-fishbone-diagram

Use when investigating the root cause of a quality defect, recurring process failure, or operational problem — to map all contributing causes across multiple categories simultaneously before selecting which cause to address.

jeffreytse/grimoire-core · 42 tokens

apply-early-intervention

Use when you detect early warning signals — technical debt accumulating, customer relationship cooling, team friction forming, process degrading — to intervene while the problem is still small and cheap, because intervention cost increases nonlinearly with delay.

jeffreytse/grimoire-core · 49 tokens

diagnose-battery-charging-problem

Use when a vehicle has starting problems, battery warning lights, or electrical symptoms — systematically testing battery condition, alternator output, and charging circuit integrity to identify the root cause before replacing components.

jeffreytse/grimoire-core · 47 tokens

diagnose-brake-system-problem

Use when experiencing brake warning signs such as noise, pulsation, pulling, soft pedal, or brake warning light to identify the fault before driving or seeking repair.

jeffreytse/grimoire-core · 39 tokens

diagnose-check-engine-light

Use when a check engine light is illuminated and you need to identify the fault code, assess severity, and decide next steps.

jeffreytse/grimoire-core · 30 tokens