A command set for Chaos Engineering, the practice of deliberately causing controlled failures to test whether a system survives them. It uses Litmus Chaos or Chaos Mesh to test Kubernetes workloads.

Use it to install a chaos-testing tool, simulate deleted pods, lost network access, CPU pressure, or drained nodes, schedule recurring tests, run GameDays, debug results, and summarize what happened.

It provides a structured way to find weaknesses before real failures do, with health checks and runbooks around each experiment. It also helps diagnose experiments that fail or become stuck.

chaos — Command for Claude Code by nitinjain999

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.

Clone the repo

git clone --depth 1 https://github.com/nitinjain999/platform-skills

Made for: Claude Code.

Or install platform-skills, the plugin that ships this one along with the rest of its 1 skill, 43 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/nitinjain999/platform-skills/chaos/github.svg)](https://agentmods.dev/commands/nitinjain999/platform-skills/chaos)

Your own site

<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/chaos"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/chaos/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/chaos"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/chaos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 97 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,092 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.

Model	Per session	Once invoked
Fable 5.1	$0.00097	$0.02092
Opus 5	$0.00048	$0.01046
Sonnet 5	$0.00019	$0.00418
Haiku 4.5	$0.00010	$0.00209

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

Security

Grade A, and why

chaos 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 10d 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.

| Probe failing | Wrong URL or PromQL | Test probe URL with `curl` from inside the namespace |

commands/chaos.md · 250 lines

How it starts

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

Design, run, and debug Chaos Engineering experiments on Kubernetes.

Interactive Wizard (fires when no arguments are provided)

When invoked with no arguments, ask before proceeding:

Q1 — Mode?

What do you need?
  1. install    — install Litmus Chaos or Chaos Mesh via Helm
  2. experiment — design a fault injection experiment
  3. schedule   — wrap an experiment in a recurring schedule
  4. gameday    — run a structured GameDay experiment
  5. debug      — diagnose a failed or stuck experiment
  6. report     — summarize results after an experiment completes

Enter 1–6 or mode name:

After collecting the mode, ask one follow-up:

install: Which tool? Litmus Chaos (recommended default) or Chaos Mesh (network/IO faults)?
experiment: Describe the workload to target — name, namespace, fault type (pod-delete / network-loss / cpu-stress / node-drain):
schedule: Provide the experiment YAML or describe the experiment to wrap in a schedule:
gameday: State the steady-state hypothesis — what metric or probe proves the system is healthy?
debug: Describe the symptom or paste the ChaosEngine/ChaosResult status:
report: Paste the ChaosResult output or describe the experiment that ran:

Then proceed into the relevant mode below.

Mode: install

Install Litmus Chaos or Chaos Mesh via Helm.

Steps:

Choose the tool:
- Litmus Chaos: CNCF graduated, ChaosCenter UI, broad experiment library → recommended default
- Chaos Mesh: CNCF incubating, fine-grained NetworkChaos, IOChaos → choose for network partitions or I/O faults

Install Litmus Chaos:

helm repo add litmuschaos https://litmuschaos.github.io/litmus-helm/
helm repo update
helm upgrade --install chaos litmuschaos/litmus \
  --namespace litmus \
  --create-namespace \
  --version 3.9.0 \
  -f examples/chaos/litmus-install-values.yaml

Install Chaos Mesh:

helm repo add chaos-mesh https://charts.chaos-mesh.org
helm repo update
helm upgrade --install chaos-mesh chaos-mesh/chaos-mesh \
  --namespace chaos-mesh \
  --create-namespace \
  --version 2.7.0 \
  -f examples/chaos/chaos-mesh-install-values.yaml

Read the full file on GitHub · 250 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.

10d ago First seen · 250 lines · 97 tokens per session scan A a41d25180442

Subscribe to this mod's changes

chaos is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 97 tokens to every session and 2,092 once invoked, about $0.0005 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-08-30.

Containers DevOps and cloud Testing ai-tools claude-code-plugin copilot-coding-agent grafana kubernetes

ia-test-browser

Run browser tests on pages affected by current PR or branch.

iliaal/whetstone · 15 tokens

ia-verify

Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.

iliaal/whetstone · 24 tokens

sm-swab

Run slop-mop's iterative development loop for this repository.

ScienceIsNeato/slop-mop · 0 tokens

responsive

Check that a Divi 5 page works across device sizes (small phones, iPhones, tablets, laptops, widescreen, ultrawide). Uses live viewport testing via a browser MCP server (Chrome DevTools or Playwright) when one is available; falls back to static CSS analysis when not.

cjsimon2/Divi5-ToolKit · 63 tokens