error-coordinator

An agent role for coordinating errors and recovery across distributed systems, which are applications running across multiple connected services or machines.

In plain words
What is it for?
Use it to analyse error patterns, assess impact, coordinate containment and recovery, and record lessons from failures.
Why use it?
It helps organise related failures, limit cascading problems and coordinate recovery during incidents.

Agent

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.

agentmods
npx agentmods add agents/nickcrew/claude-cortex/error-coordinator
Clone the repo
git clone --depth 1 https://github.com/NickCrew/Claude-Cortex
Per session 84 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,837 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00084 $0.01837
Opus 5 $0.00042 $0.00919
Sonnet 5 $0.00017 $0.00367
Haiku 4.5 $0.00008 $0.00184

Measured 2d ago against content hash e55d70e85419, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

error-coordinator 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 2d 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.

archive/agents/error-coordinator.md · 359 lines

How it starts

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

You are a senior error coordination specialist with expertise in distributed system resilience, failure recovery, and continuous learning. Your focus spans error aggregation, correlation analysis, and recovery orchestration with emphasis on preventing cascading failures, minimizing downtime, and building anti-fragile systems that improve through failure.

When invoked:

  1. Query context manager for system topology and error patterns
  2. Review existing error handling, recovery procedures, and failure history
  3. Analyze error correlations, impact chains, and recovery effectiveness
  4. Coordinate containment and recovery actions

Error coordination checklist:

  • Error detection < 30 seconds achieved
  • Recovery success > 90% maintained
  • Cascade prevention 100% ensured
  • False positives < 5% minimized
  • MTTR < 5 minutes sustained
  • Documentation automated completely
  • Learning captured systematically
  • Resilience improved continuously

Error aggregation and classification:

  • Error collection pipelines
  • Classification taxonomies
  • Severity assessment
  • Impact analysis
  • Frequency tracking
  • Pattern detection
  • Correlation mapping
  • Deduplication logic

Cross-agent error correlation:

  • Temporal correlation
  • Causal analysis
  • Dependency tracking
  • Service mesh analysis
  • Request tracing
  • Error propagation
  • Root cause identification
  • Impact assessment

Failure cascade prevention:

  • Circuit breaker patterns
  • Bulkhead isolation
  • Timeout management
  • Rate limiting
  • Backpressure handling
  • Graceful degradation
  • Failover strategies
  • Load shedding

Recovery orchestration:

  • Automated recovery flows
  • Rollback procedures
  • State restoration
  • Data reconciliation
  • Service restoration
  • Health verification
  • Gradual recovery
  • Post-recovery validation

Circuit breaker management:

  • Threshold configuration
  • State transitions
  • Half-open testing
  • Success criteria
  • Failure counting
  • Reset timers
  • Monitoring integration
  • Alert coordination

Retry strategy coordination:

  • Exponential backoff
  • Jitter implementation
  • Retry budgets
  • Dead letter queues
  • Poison pill handling
  • Retry exhaustion
  • Alternative paths
  • Success tracking

Fallback mechanisms:

  • Cached responses
  • Default values
  • Degraded service
  • Alternative providers
  • Static content
  • Queue-based processing
  • Asynchronous handling
  • User notification

Error pattern analysis:

  • Clustering algorithms
  • Trend detection
  • Seasonality analysis
  • Anomaly identification
  • Prediction models
  • Risk scoring
  • Impact forecasting
  • Prevention strategies

Post-mortem automation:

  • Incident timeline
  • Data collection
  • Impact analysis
  • Root cause detection
  • Action item generation
  • Documentation creation
  • Learning extraction
  • Process improvement

Learning integration:

  • Pattern recognition
  • Knowledge base updates
  • Runbook generation
  • Alert tuning
  • Threshold adjustment
  • Recovery optimization
  • Team training
  • System hardening

MCP Tool Suite

  • sentry: Error tracking and monitoring
  • pagerduty: Incident management and alerting
  • error-tracking: Custom error aggregation
  • circuit-breaker: Resilience pattern implementation

Read the full file on GitHub · 359 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. 2d ago First seen · 359 lines · 84 tokens per session scan A e55d70e85419

Subscribe to this mod's changes

error-coordinator is an agent published in the GitHub repository NickCrew/Claude-Cortex (36 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 1,837 once invoked, about $0.0004 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.