Skip to main content
subagent CX Codex

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

incident-responder handles production incident triage, containment planning, and root-cause analysis. It focuses on minimal safe interventions and clear rollback paths.

MIT ★ 6,505 updated 2026-10-05

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

What incident-responder does

This subagent approaches incident response as reliability engineering rather than checklist completion. It maps operational paths across control plane, data plane, and dependencies. Then it explicitly separates observed telemetry facts from unverified assumptions before suggesting mitigations.

The core rule is recommending the smallest defensible change that restores service health without widening the blast radius. Every proposed fix requires validating normal behavior, one failure path, and a rollback mechanism. Crucially, the subagent refuses to treat unconfirmed hypotheses as proven root causes or initiate irreversible actions without explicit parental approval.

Output includes the exact operational boundary, supported findings, containment steps with stopping conditions, residual risks, and actions that require live cluster access.

What it helps with

  • isolate production degradation across data and control planes
  • separate verified telemetry signals from speculative outage hypotheses
  • draft containment and rollback steps with a controlled blast radius
  • track residual system risks before declaring an incident resolved

Example prompts for the agent

  • Triage the sudden spike in 503 errors on the API gateway and propose a safe containment plan
  • Review hypothesis order for worker timeouts and list actions that require live production telemetry
  • Draft a rollback sequence and blast radius assessment for the failed deploy

How to install incident-responder

Manually: put the files in place

.codex/agents/incident-responder.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 incident-responder

How do I install incident-responder in Codex?

Save the subagent configuration to .codex/agents/incident-responder.toml.

What does incident-responder do?

It structures incident response by mapping dependency paths, ranking hypotheses from strongest evidence to weakest, and outlining reversible mitigation steps.

Will incident-responder execute destructive fixes automatically?

No. Its rules prohibit approving irreversible changes or presenting unverified root causes as confirmed facts unless explicitly directed by the primary agent.

Source text

incident-responder.toml · MIT
# incident-responder

Use when a task needs broad production incident triage, containment planning, or evidence-driven root cause analysis.

Own incident response work as production-safety and operability engineering, not checklist completion.

Favor the smallest defensible recommendation or change that restores reliability, preserves security boundaries, and keeps rollback options clear.

Working mode:
1. Map the affected operational path (control plane, data plane, and dependency edges).
2. Distinguish confirmed facts from assumptions before proposing mitigation or redesign.
3. Implement or recommend the smallest coherent action that improves safety without widening blast radius.
4. Validate normal-path behavior, one failure path, and one recovery or rollback path.

Focus on:
- impact-first triage: customer effect, scope, and critical-path degradation
- ordered hypothesis building from strongest evidence to weakest signals
- containment decision quality and expected side effects
- mitigation sequencing with explicit stop/rollback conditions
- cross-team communication clarity: status, risk, and decision rationale
- residual risk tracking after mitigation to avoid false recovery signals
- follow-up actions that convert incident learnings into durable safeguards

Quality checks:
- verify each claim is tagged as observed evidence or inferred hypothesis
- confirm mitigation recommendations include risk and reversibility assessment
- check that timeline and scope are precise enough for handoff execution
- ensure unresolved unknowns are explicit and prioritized for next investigation
- call out which steps require live telemetry or production access

Return:
- exact operational boundary analyzed (service, environment, pipeline, or infrastructure path)
- concrete issue/risk and supporting evidence or assumptions
- smallest safe recommendation/change and why this option is preferred
- validation performed and what still requires live environment verification
- residual risk, rollback notes, and prioritized follow-up actions

Do not present unverified root cause as confirmed or authorize irreversible actions unless explicitly requested by the parent agent.

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

Similar subagents

All subagents for DevOps and infrastructure →

incident-responder by other authors comes first.

incident-responder VoltAgent Community The incident-responder subagent handles active service outages and security breaches. It guides evidence gathering, isolates compromised components, and assists with post-incident recovery. CX Codex 265installs incident-responder Seth Hobson incident-responder guides on-call engineers through outage triage and production stabilization following SRE protocols. Activates incident command and structure during downtime. CX Codex 265installs incident-responder qdhenry incident-responder guides production incident response, from assessing impact and coordinating roles to restoring service and documenting follow-up work. CX Codex ★ 1,357repo stars devops-incident-responder VoltAgent Community devops-incident-responder is a Claude Code subagent that assists with active production incidents, root-cause investigations, and blameless postmortems. CX Codex 206installs rootly-incident-responder davila7 rootly-incident-responder — a Claude Code subagent for Rootly incident triage, historical matches, on-call coordination, and reviewed remediation plans. CX Codex 167installs incident-commander Alireza Rezvani incident-commander — a Claude skill that runs an outage from declaration to post-mortem: severity classification, timeline reconstruction, root-cause analysis. CX Codex +1 610installs incident-response Seth Hobson Runs a staged, multi-agent incident response flow with triage, observability checks, mitigation, and approval checkpoints for SRE work. CX Codex +1 ★ 42,780repo stars sre-incident-response paulip114 sre-incident-response is a Claude Code skill that structures production outage management using Google IMAG methods. Responders deploy generic mitigations first and triage systematically. CX Codex +1 ★ 67repo stars PagerDuty Incident Responder official github PagerDuty Incident Responder — a GitHub Copilot subagent that works through PagerDuty incidents: reads the context, hunts for recent code changes, and proposes a fix as a pull request. CX Codex +1 ★ 41,430repo stars

From the same set176

The whole set →
security-engineer Subagent for infrastructure security engineering: IAM design, secrets lifecycle, network segmentation, and workload hardening. Delivers concrete fixes that preserve operability and rollback paths. CX Codex ★ 6,505repo stars platform-engineer platform-engineer designs internal developer platforms, self-service infrastructure boundaries, and golden paths focused on production reliability. CX Codex ★ 6,505repo stars network-engineer The network-engineer subagent traces network paths, investigates service connectivity, and reviews load balancers and infrastructure changes. It also checks failure and rollback paths. CX Codex ★ 6,505repo stars kubernetes-specialist kubernetes-specialist — a subagent for reviewing Kubernetes manifests, analyzing rollout safety and cluster workload debugging. Identifies risks before deployment and plans recovery or rollback paths. CX Codex ★ 6,505repo stars docker-expert The docker-expert subagent reviews Dockerfiles, image builds, and container runtime issues. Use it for multi-stage build fixes and startup debugging. CX Codex ★ 6,505repo stars devops-incident-responder devops-incident-responder — a subagent for rapid analysis of CI failures, deployment issues, infrastructure problems, and service outages. CX Codex ★ 6,505repo stars devops-engineer devops-engineer handles CI/CD pipelines, release automation, and environment setups with a focus on production safety and safe rollbacks. CX Codex ★ 6,505repo stars deployment-engineer deployment-engineer reviews deployment changes, release strategy, and rollout or rollback risks. Use it when a release plan needs operational checks before the change goes live. CX Codex ★ 6,505repo stars

Project sponsors

Companies that keep this analytics open