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.
npx skills add nitinjain999/platform-skills --skill chaosgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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.
[](https://agentmods.dev/skills/nitinjain999/platform-skills/chaos)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/chaos"><img src="https://agentmods.dev/badge/skills/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.
<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/chaos"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/chaos.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.5 | $0.00039 | $0.00837 |
| Sonnet 5.5 | $0.00019 | $0.00418 |
| Haiku 4.5 | $0.00010 | $0.00209 |
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 5d 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 | 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
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.
- 5d ago First seen · 250 lines · 97 tokens per session scan A a41d25180442
chaos is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed 3d ago), licensed Apache-2.0. It adds 97 tokens to every session and 2,092 once invoked, about $0.0004 per session on Opus 5.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-10-12.
Other skills, from other repositories
ia-c-systems
C patterns for systems code, libraries, and native extensions: module layout, function decomposition, status-enum errors, memory safety, undefined behavior, and performance measurement. Use when writing, reviewing, refactoring, or debugging C, working with malloc lifetimes, buffer overflows, sanitizers, or Valgrind…
ia-verification-before-completion
Enforces fresh verification evidence before any completion claim. Use when about to claim "tests pass", "bug fixed", "done", "ready to merge", handing off work, or before editing when a request has ambiguous scope.
debugging
Systematic root-cause debugging: reproduce, investigate, hypothesize, fix with verification. Use when asked to "debug this", "fix this bug", "why is this failing", "troubleshoot", or mentions errors, stack traces, broken tests, flaky tests, regressions, or unexpected behavior.
rubber-ducky
Use when you've planned a non-trivial change and are about to implement it, finished a complex or multi-file piece of work, just wrote tests, or are stuck on repeated failures — and any time the user says "rubber duck this", "rubber ducky", "get a second opinion", "sanity-check my plan", "poke holes in this", "what am…
analyze-misfires
Analyze Whetstone skill injection misfires when asked to investigate overly broad triggers or irrelevant injected skills.
diagnose-negatives
Investigate negative session feedback for a Whetstone skill when asked to diagnose its failures.