chaos-engineering-resilience

chaos-engineering-resilience is a skill for Claude Code from summarybotng/summarybot-ng. It costs 40 tokens per session (1,126 once invoked), scanned A, original, MIT.

A method for deliberately introducing controlled failures into systems to check whether they recover correctly. Chaos engineering is this kind of resilience testing for distributed systems and disaster recovery.

In plain words
What is it for?
Use it to test fault tolerance, validate recovery plans, measure failure impact, and improve operational runbooks.
Why use it?
It reveals weaknesses that normal tests may miss when networks, machines, disks, or other infrastructure fail.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to test fault tolerance, validate recovery plans, measure failure impact, and improve operational runbooks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/summarybotng/summarybot-ng/chaos-engineering-resilience
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 summarybotng/summarybot-ng --skill chaos-engineering-resilience
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

Made for: Claude Code.

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 chaos-engineering-resilience

README.md
[![agentmods](https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/chaos-engineering-resilience/github.svg)](https://agentmods.dev/skills/summarybotng/summarybot-ng/chaos-engineering-resilience)
Your own site
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/chaos-engineering-resilience"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/chaos-engineering-resilience/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 chaos-engineering-resilience

Your own site · 80×15
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/chaos-engineering-resilience"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/chaos-engineering-resilience.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,126 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00040 $0.01126
Opus 5 $0.00020 $0.00563
Sonnet 5 $0.00008 $0.00225
Haiku 4.5 $0.00004 $0.00113

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

Security

Grade A, and why

chaos-engineering-resilience 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 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.

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.

.claude/skills/chaos-engineering-resilience/SKILL.md · 164 lines

How it starts

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

Chaos Engineering & Resilience Testing

<default_to_action> When testing system resilience or injecting failures:

  1. DEFINE steady state (normal metrics: error rate, latency, throughput)
  2. HYPOTHESIZE system continues in steady state during failure
  3. INJECT real-world failures (network, instance, disk, CPU)
  4. OBSERVE and measure deviation from steady state
  5. FIX weaknesses discovered, document runbooks, repeat

Quick Chaos Steps:

  • Start small: Dev → Staging → 1% prod → gradual rollout
  • Define clear rollback triggers (error_rate > 5%)
  • Measure blast radius, never exceed planned scope
  • Document findings → runbooks → improved resilience

Critical Success Factors:

  • Controlled experiments with automatic rollback
  • Steady state must be measurable
  • Start in non-production, graduate to production </default_to_action>

Quick Reference Card

When to Use

  • Distributed systems validation
  • Disaster recovery testing
  • Building confidence in fault tolerance
  • Pre-production resilience verification

Failure Types to Inject

Category Failures Tools
Network Latency, packet loss, partition tc, toxiproxy
Infrastructure Instance kill, disk failure, CPU Chaos Monkey
Application Exceptions, slow responses, leaks Gremlin, LitmusChaos
Dependencies Service outage, timeout WireMock

Blast Radius Progression

Dev (safe) → Staging → 1% prod → 10% → 50% → 100%
     ↓           ↓         ↓        ↓
  Learn      Validate   Careful   Full confidence

Steady State Metrics

Metric Normal Alert Threshold
Error rate < 0.1% > 1%
p99 latency < 200ms > 500ms
Throughput baseline -20%

Chaos Experiment Structure

// Chaos experiment definition
const experiment = {
  name: 'Database latency injection',
  hypothesis: 'System handles 500ms DB latency gracefully',
  steadyState: {
    errorRate: '< 0.1%',
    p99Latency: '< 300ms'
  },
  method: {
    type: 'network-latency',
    target: 'database',
    delay: '500ms',
    duration: '5m'
  },
  rollback: {
    automatic: true,
    trigger: 'errorRate > 5%'
  }
};

Read the full file on GitHub · 164 lines

Files

What ships with it

3 files 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.

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 · 164 lines · 40 tokens per session scan A 2f6a1371957d

Subscribe to this mod's changes

chaos-engineering-resilience is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 3mo ago), licensed MIT. It adds 40 tokens to every session and 1,126 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-09-03.

Related

Other skills, from other repositories

chaos-engineering

Chaos Engineering: Designs and reviews resilience testing strategies — fault injection, game days, failure mode analysis, and blast radius assessment. Covers chaos experiments for distributed systems, database failures, network partitions, and dependency outages. Use when the user mentions chaos engineering…

camilooscargbaptista/cto-toolkit · 86 tokens

agent-harness-fault-injection

Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.

sickn33/agentic-awesome-skills · 34 tokens

Advanced Chaos Engineering

Advanced chaos engineering patterns using Chaos Monkey, Litmus, and Gremlin for testing distributed system resilience under failure conditions.

PramodDutta/qaskills · 27 tokens

chaos-engineering

Use when planning, running, or learning from chaos engineering experiments. Triggers on "chaos experiment", "fault injection", "gameday", "resilience test", "blast radius", "steady state", "abort criteria", "Chaos Toolkit", "Chaos Mesh", "Litmus", "Gremlin", "AWS FIS", or any deliberate failure-injection question.…

bestagentkits/agency-skills · 152 tokens

Kubernetes Chaos Testing

Chaos testing for Kubernetes workloads using Chaos Mesh, Litmus, and custom fault injection for pod, network, and disk failures.

PramodDutta/qaskills · 30 tokens

chaos-fault-injection

Deliberately inject faults — dropped connections, corrupted writes, latency, malformed responses, resource exhaustion — and assert the system's expected recovery (escalation, hardstop, rollback).

andreibesleaga/GABBE · 44 tokens