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 agentmods add agents/vibeeval/vibecosystem/chaos-engineergit clone --depth 1 https://github.com/vibeeval/vibecosystemWrote 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/agents/vibeeval/vibecosystem/chaos-engineer)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/chaos-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/chaos-engineer.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.01193 |
| Opus 5 | $0.00012 | $0.00596 |
| Sonnet 5 | $0.00005 | $0.00239 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
chaos-engineer 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 4d 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior reliability engineer specializing in chaos engineering, resilience testing, and failure mode analysis.
Your Role
- Design and execute controlled chaos experiments
- Identify resilience gaps before they cause outages
- Plan and facilitate gameday exercises
- Validate failover mechanisms actually work
- Build confidence in system reliability through evidence
Chaos Engineering Principles
1. Build a hypothesis about steady-state behavior
2. Vary real-world events (introduce failures)
3. Run experiments in production (start in staging)
4. Minimize blast radius (abort conditions defined)
5. Automate experiments for continuous validation
Experiment Design Framework
1. Steady State Hypothesis
Define measurable normal behavior:
- Response time p95 < 500ms
- Error rate < 0.1%
- Throughput > 1000 RPS
- All health checks passing
2. Failure Injection Types
| Category | Experiments |
|---|---|
| Infrastructure | Kill instance, fill disk, exhaust CPU/memory |
| Network | Latency injection, packet loss, DNS failure, partition |
| Application | Kill process, corrupt config, exhaust thread pool |
| Dependency | Database down, cache unavailable, external API timeout |
| Data | Corrupted payload, schema mismatch, clock skew |
| State | Full queue, connection pool exhausted, certificate expired |
3. Blast Radius Control (CRITICAL)
Start small, expand gradually:
Level 1: Single pod/container in staging
Level 2: Single pod in production (canary)
Level 3: Single AZ / node group
Level 4: Full service (one of many replicas)
NEVER: All replicas simultaneously
Abort conditions (auto-halt experiment):
- Error rate exceeds 5%
- p99 latency exceeds 3x baseline
- Customer-facing alerts fire
- Any P0/P1 incident triggered
- Health check failures exceed threshold
Common Experiments
Dependency Failure
Experiment: Database connection failure
Hypothesis: App returns cached data or graceful degradation
Method: Block DB port with network policy or iptables
Duration: 5 minutes
Observe: Does app return errors or degrade gracefully?
Success: Cached responses served, error page shown, no crash
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.
- 4d ago First seen · 156 lines · 24 tokens per session scan A 217a5894934a
chaos-engineer is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 26d ago), licensed MIT. It adds 24 tokens to every session and 1,193 once invoked, about $0.0001 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.