Skip to main content
subagent CX Codex

chaos-engineer · voltagent/awesome-codex-subagents — Codex subagent: what it does, how to install

chaos-engineer evaluates dependency resilience, plans controlled fault injection, and identifies flaws in fallback logic or timeout handling.

MIT ★ 6,505 updated 2026-10-05

Install into Codex · Manually: put the files in place All methods and platforms ↓
.codex/agents/chaos-engineer.toml
Open on GitHub

What chaos-engineer does

This subagent inspects failure boundaries and dependency chains. It separates confirmed evidence from unverified assumptions, then inspects retry policies, fallback logic, and baseline health signals.

Every proposed experiment requires blast-radius guardrails, defined stop criteria, and measurable indicators. The agent is explicitly forbidden from running production fault injection without parent-agent approval and strict safety controls. Output includes inspected scopes, residual risks, and the smallest fixes required to mitigate user-facing outages.

What it helps with

  • plan controlled fault-injection experiments with defined stop criteria
  • assess fallback logic and retry behavior under dependency outages
  • define steady-state signals to monitor service regressions
  • isolate high-risk failure boundaries in modified code

Example prompts for the agent

  • Analyze our payment service resilience if the third-party gateway starts timing out
  • Create a safe fault-injection plan to verify cache failover behavior

How to install chaos-engineer

Manually: put the files in place

.codex/agents/chaos-engineer.toml

Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about chaos-engineer

How do I install chaos-engineer in Codex?

Place the agent configuration into .codex/agents/chaos-engineer.toml in your project repository.

What does the chaos-engineer subagent do?

It analyzes failure surfaces, verifies degraded modes and recovery paths, and drafts safety-checked chaos experiments.

Can chaos-engineer inject faults directly into production?

No. It strictly requires parent-agent approval and explicit guardrails before proposing any live-environment fault injection.

Source text

chaos-engineer.toml · MIT
# chaos-engineer

Use when a task needs resilience analysis for dependency failure, degraded modes, recovery behavior, or controlled fault-injection planning.

Own chaos and resilience engineering work as evidence-driven quality and risk reduction, not checklist theater.

Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.

Working mode:
1. Map the changed or affected behavior boundary and likely failure surface.
2. Separate confirmed evidence from hypotheses before recommending action.
3. Implement or recommend the minimal intervention with highest risk reduction.
4. Validate one normal path, one failure path, and one integration edge where possible.

Focus on:
- failure hypothesis definition tied to concrete dependency or capacity risks
- steady-state signal selection to determine whether service health regresses
- blast-radius controls and safety guardrails for experiment execution
- degradation behavior, fallback logic, and timeout/retry dynamics
- recovery behavior and rollback/abort conditions during experiments
- observability quality needed to interpret experiment outcomes reliably
- post-experiment learning translation into reliability backlog actions

Quality checks:
- verify each proposed experiment has explicit hypothesis, scope, and stop criteria
- confirm safety controls prevent uncontrolled customer impact
- check that expected and unexpected outcomes both map to actionable next steps
- ensure reliability metrics are defined before fault injection planning
- call out live-environment prerequisites and approvals needed for execution

Return:
- exact scope analyzed (feature path, component, service, or diff area)
- key finding(s) or defect/risk hypothesis with supporting evidence
- smallest recommended fix/mitigation and expected risk reduction
- what was validated and what still needs runtime/environment verification
- residual risk, priority, and concrete follow-up actions

Do not recommend production fault injection without explicit guardrails and parent-agent approval.

© VoltAgent · MIT · VoltAgent/awesome-codex-subagents

Similar subagents

All subagents for Testing and QA →

chaos-engineer by other authors comes first.

chaos-engineer VoltAgent Community The chaos-engineer subagent plans controlled failure experiments and checks how a system recovers. Use it to prepare for incidents or run a game day. CX Codex 267installs chaos-engineering kindlmann chaos-engineering plans hypothesis-driven fault injection experiments to test system resilience. Useful when preparing game days or verifying fallbacks against network and service outages. CX Codex +1 1,300installs qe-chaos-resilience proffesor-for-testing qe-chaos-resilience — a skill for Claude Code, Codex, Cursor and other agents that injects controlled faults into distributed systems and checks recovery behavior. Runs during circuit breaker, failover, and retry logic validation. CX Codex +1 123installs aws-fault-injection-service aws Designs, runs, and analyzes chaos experiments in AWS Fault Injection Service. It helps test application resilience against AZ outages, network packet loss, and compute failures. CX Codex +1 1,800installs chaos-engineering-resilience proffesor-for-testing chaos-engineering-resilience — a skill for injecting controlled failures into distributed systems, verifying recovery mechanisms, and validating resilience. Catches weaknesses before users do. CX Codex +1 138installs azure-chaos-studio MicrosoftDocs Skill for Azure Chaos Studio setup: experiments, workspaces, AKS agents, Private Link, and migration from classic experiments. CX Codex +1 170installs performance-engineer VoltAgent Community performance-engineer — a Claude Code subagent designed to identify performance bottlenecks across code, databases, and infrastructure under heavy load. CX Codex 671installs

From the same set176

The whole set →
error-detective error-detective — a subagent for fast analysis of logs, exceptions, and stack traces. Pinpoints the probable failure source by separating the primary fault from downstream cascade effects. CX Codex ★ 6,505repo stars debugger debugger isolates bugs across code paths, stack traces, and failing test runs. It pinpoints the defect and recommends a minimal fix. CX Codex ★ 6,505repo stars compliance-auditor The compliance-auditor subagent reviews controls, auditability, policy alignment, and evidence gaps in regulated workflows. CX Codex ★ 6,505repo stars code-reviewer code-reviewer — a subagent for comprehensive code review covering maintainability, design, and risk factors beyond correctness. Surfaces issues in error handling, data contracts, and state mutations that threaten production stability. CX Codex ★ 6,505repo stars browser-debugger The browser-debugger subagent reproduces browser failures, gathers UI and network evidence, and helps trace client-side bugs to their cause. CX Codex ★ 6,505repo stars architect-reviewer architect-reviewer — a subagent for architecture review: module coupling, system boundaries, failure risk, long-term maintainability. Analyzes design and recommends minimal interventions that reduce risk. CX Codex ★ 6,505repo stars anti-ui-slop-reviewer anti-ui-slop-reviewer serves as an adversarial finish-gate reviewer for web and iOS screens. Catches generic AI patterns, missing interaction states, and design-system drift. CX Codex ★ 6,505repo stars ai-writing-auditor ai-writing-auditor is a subagent that checks prose for AI-writing signals, rewrites flagged passages, and explains edits. It reviews posts, technical docs, and emails. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open