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 an8079/take-skills --skill chaos-engineeringgit clone --depth 1 https://github.com/an8079/take-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/an8079/take-skills/chaos-engineering)<a href="https://agentmods.dev/skills/an8079/take-skills/chaos-engineering"><img src="https://agentmods.dev/badge/skills/an8079/take-skills/chaos-engineering/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/an8079/take-skills/chaos-engineering"><img src="https://agentmods.dev/badge/skills/an8079/take-skills/chaos-engineering.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.00064 | $0.02267 |
| Opus 5 | $0.00032 | $0.01133 |
| Sonnet 5 | $0.00013 | $0.00453 |
| Haiku 4.5 | $0.00006 | $0.00227 |
Grade A, and why
chaos-engineering 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chaos Engineering — Proactive Resilience Discovery
Core Philosophy
"Break things on purpose to build unbreakable systems."
Chaos engineering is the discipline of experimenting on a system to build confidence in its resilience. Unlike reactive debugging, it proactively injects faults before users notice them.
Key Principle: Steady-State Hypothesis First
Every experiment starts with a steady-state hypothesis — a measurable statement about your system's behavior under normal conditions.
Steady State = "Normal behavior we expect to observe"
Hypothesis = "Injecting fault X will [not change / degrade] the steady state"
Never run chaos without first defining steady state.
Experiment Design Pattern
1. Define steady-state hypothesis
2. Inject the smallest possible fault
3. Monitor for deviation from steady state
4. Roll back immediately if hypothesis fails
5. Automate and repeat
Common Faults to Inject
Network Layer
| Fault | Command/Method | Impact |
|---|---|---|
| Latency | tc qdisc add dev eth0 netem delay 100ms |
API timeouts |
| Packet loss | tc qdisc add dev eth0 netem loss 5% |
Intermittent errors |
| DNS failure | /etc/hosts manipulation |
Service discovery breaks |
| Partition | iptables -A INPUT -s <ip> |
Network split |
Resource Layer
| Fault | Method | Impact |
|---|---|---|
| CPU spike | stress-ng --cpu 1 --timeout 30s |
Throttling, slow responses |
| Memory leak | Allocate until OOM | Pod evictions |
| Disk full | dd if=/dev/zero of=/tmp/bigfile |
Write failures |
| File descriptor exhaustion | ulimit -n 1024 in container |
Connection pooling breaks |
Application Layer
| Fault | Method | Impact |
|---|---|---|
| Kill pod | kubectl delete pod |
Restart tolerance |
| Container restart | docker restart |
Session/state recovery |
| Config map change | kubectl patch |
Behavior drift |
| Secret deletion | kubectl delete secret |
Auth failures |
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 · 300 lines · 64 tokens per session scan A 4122ad6cd9a9
chaos-engineering is a skill published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 2,267 once invoked, about $0.0003 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.