chaos-experiment

chaos-experiment is a skill for Claude Code from rjmurillo/ai-agents. It costs 84 tokens per session (2,925 once invoked), scanned A, original, MIT.

A guide for designing chaos engineering experiments, where controlled failures are introduced to check whether a system continues working. It covers normal operating behavior, predictions, failure plans, execution, and results.

In plain words
What is it for?
Use it to plan game days, failure-injection exercises, API gateway failover tests, circuit-breaker tests, and database resilience checks.
Why use it?
It helps teams test resilience in a controlled way instead of discovering weaknesses during an outage.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Part of the project-toolkit plugin — 113 skills, 26 commands, 33 agents, 4 hooks shipped together

Good fit Use it to plan game days, failure-injection exercises, API gateway failover tests, circuit-breaker tests, and database resilience checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rjmurillo/ai-agents/chaos-experiment
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 rjmurillo/ai-agents --skill chaos-experiment
Clone the repo
git clone --depth 1 https://github.com/rjmurillo/ai-agents

Made for: Claude Code.

Or install project-toolkit, the plugin that ships this one along with the rest of its 113 skills, 26 commands, 33 agents, 4 hooks.

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-experiment

README.md
[![agentmods](https://agentmods.dev/badge/skills/rjmurillo/ai-agents/chaos-experiment/github.svg)](https://agentmods.dev/skills/rjmurillo/ai-agents/chaos-experiment)
Your own site
<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/chaos-experiment"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/chaos-experiment/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-experiment

Your own site · 80×15
<a href="https://agentmods.dev/skills/rjmurillo/ai-agents/chaos-experiment"><img src="https://agentmods.dev/badge/skills/rjmurillo/ai-agents/chaos-experiment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,925 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Prompt Injection · line 361
    Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.
    Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
  • low Excessive Agency · line 240
    Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.
    Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
How audits are shown
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.00084 $0.02925
Opus 5 $0.00042 $0.01463
Sonnet 5 $0.00017 $0.00585
Haiku 4.5 $0.00008 $0.00293

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

Security

Grade A, and why

chaos-experiment 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/generate_experiment.py, scripts/validate_experiment.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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-experiment/SKILL.md · 362 lines

How it starts

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

Chaos Experiment Designer

Design rigorous chaos engineering experiments that build confidence in system resilience.

Quick Start

# Describe what you want to test:
"Design a chaos experiment for our API gateway failover"
"Plan a game day for database resilience"
"Test whether our circuit breakers work under load"

The skill guides you through 6 phases: Scope, Baseline, Hypothesis, Injection, Execute, Analyze.

Triggers

  • chaos experiment
  • failure injection
  • game day
  • test resilience
  • chaos engineering

Quick Reference

Phase Purpose Output
1. Scope Define system boundaries and objectives System under test, success criteria
2. Baseline Establish steady state metrics Quantified normal behavior
3. Hypothesis Form falsifiable hypothesis Clear prediction statement
4. Injection Design failure scenarios Injection plan with blast radius
5. Execute Run controlled experiment Observation log
6. Analyze Compare actual vs expected Findings and action items

When to Use

Use this skill when:

  • Planning a game day or failure injection exercise
  • Building confidence in system resilience before production launch
  • Investigating whether auto-scaling, circuit breakers, or failover mechanisms work as designed
  • After a real incident, to validate that fixes prevent recurrence

Use threat-modeling instead when:

  • Identifying security threats (not resilience)
  • Evaluating attack surfaces rather than failure modes

Use pre-mortem instead when:

  • Identifying project risks (not infrastructure failures)
  • Working at planning stage before any system exists

Process Overview

Scope → Baseline → Hypothesis → Injection Plan → Execute → Analyze
  │         │           │             │              │          │
  └─ Stakeholder sign-off
              └─ 7-30 day metric collection
                          └─ Falsifiable prediction
                                        └─ Rollback-ready plan
                                                       └─ Observation log
                                                                  └─ Verdict + action items

Read the full file on GitHub · 362 lines

Files

What ships with it

6 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 · 362 lines · 84 tokens per session scan A 3bebfe39adb5

Subscribe to this mod's changes

chaos-experiment is a skill published in the GitHub repository rjmurillo/ai-agents (45 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 2,925 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-09-03.

Related

Other skills, from other repositories

develop-web-game

Use when Codex is building or iterating on a web game (HTML/JS) and needs a reliable development + testing loop: implement small changes, run a Playwright-based test script with short input bursts and intentional pauses, inspect screenshots/text, and review console errors with rendergametotext.

netease-youdao/LobsterAI · 64 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

browser4-cli

Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

platonai/Browser4 · 52 tokens

auto-canary

A deployment health-check skill for testing whether a recently deployed or staging website is working. It runs build, end-to-end, and browser checks, then reports a pass, warning, or failure.

Insajin/autopus-adk · 24 tokens

testing-strategy

A testing guide that explains how to combine unit, integration, contract, and end-to-end tests. End-to-end tests check complete user flows, while integration tests check components working together.

Insajin/autopus-adk · 20 tokens

CI/CD Pipeline Config

CI/CD pipeline configuration skill for test automation, covering GitHub Actions, Jenkins, GitLab CI, test parallelization, reporting, and artifact management.

PramodDutta/qaskills · 35 tokens