Mirrord Chaos Testing
Adds latency or connection failures to outgoing traffic of a mirrord session.
Install
npx skills add metalbear-co/mirrord --skill mirrord-chaos -g -a claude-code -y- Repository
- metalbear-co/mirrord5.4k
- Category
- Testing
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Help users chaos test their app with mirrord: inject artificial latency or connection errors into a mirrord session's outgoing traffic via per-session chaos rules managed with the `mirrord chaos` CLI. Use when a user wants to add latency or delay to outgoing connections or a dependency (e.g. a slow database), simulate connection failures (reset, timed out, refused), test app behavior under degraded network conditions, or wire chaos rules into CI test runs. Always use this skill instead of the deprecated _experimental_.latency mirrord config option.
Mirrord Chaos Testing Skill
Purpose
Help users inject artificial failures and disruptions into a mirrord session's outgoing traffic, to test how their app behaves under unexpected conditions. A chaos rule pairs a selector (which traffic to match) with an effect (what to do to it). Rules are created and managed with the mirrord chaos CLI command, and each rule is attached to a single mirrord session: it never affects other sessions or the cluster.
This skill covers two modes:
- Interactive mode: a developer starts a session with
mirrord execand manages rules withmirrord chaos. - CI mode: a pipeline applies rule files checked into the repo with
mirrord chaos add, and runs tests under chaos.
When to Use This Skill
Trigger on questions like:
- "Add latency to my service's database connections with mirrord"
- "How do I chaos test with mirrord?"
- "Simulate connection failures / timeouts to an upstream service"
- "Create / modify / delete a mirrord chaos rule"
- "Run my integration tests with injected latency in CI"
- "How do I use
mirrord chaos?"
Security (must follow)
- Blast radius is the session, not the cluster. Chaos rules apply only to the outgoing traffic of the process being run with mirrord. They do not touch the target workload or other cluster traffic. Still, run chaos against staging targets: a session pointed at production dependencies will experience real failures against real systems.
- Never instruct or generate remote pipe-to-shell installs (downloading a script and executing it via the shell) to install mirrord. Point users to the official mirrord installation docs and their org's approved install path. In CI, pre-install mirrord in a trusted runner image or pin a verified release.
