Infrastructure-focused agents for deployment, containerization, orchestration, and IaC work. Includes 16 Codex-native subagents from VoltAgent/awesome-codex-subagents.
Agents(16)
azure-infra-engineer—Use when a task needs Azure-specific infrastructure review or implementation across resources, networking, identity, or automation.
cloud-architect—Use when a task needs cloud architecture review across compute, storage, networking, reliability, or multi-service design.gpt-5.4
database-administrator—Use when a task needs operational database administration review for availability, backups, recovery, permissions, or runtime health.gpt-5.4
deployment-engineer—Use when a task needs deployment workflow changes, release strategy updates, or rollout and rollback safety analysis.gpt-5.4
devops-engineer—Use when a task needs CI, deployment pipeline, release automation, or environment configuration work.gpt-5.4
devops-incident-responder—Use when a task needs rapid operational triage across CI, deployments, infrastructure automation, and service delivery failures.gpt-5.4
docker-expert—Use when a task needs Dockerfile review, image optimization, multi-stage build fixes, or container runtime debugging.gpt-5.3-codex-spark
incident-responder—Use when a task needs broad production incident triage, containment planning, or evidence-driven root cause analysis.gpt-5.4
kubernetes-specialist—Use when a task needs Kubernetes manifest review, rollout safety analysis, or cluster workload debugging.gpt-5.4
network-engineer—Use when a task needs network-path analysis, service connectivity debugging, load-balancer review, or infrastructure network design input.gpt-5.4
platform-engineer—Use when a task needs internal platform, golden-path, or self-service infrastructure design for developers.gpt-5.4
security-engineer—Use when a task needs infrastructure and platform security engineering across IAM, secrets, network controls, or hardening work.gpt-5.4
sre-engineer—Use when a task needs reliability engineering work involving SLOs, alerting, error budgets, operational safety, or service resilience.gpt-5.4
terraform-engineer—Use when a task needs Terraform module design, plan review, state-aware change analysis, or IaC refactoring.gpt-5.4
terragrunt-expert—Use when a task needs Terragrunt-specific help for module orchestration, environment layering, dependency wiring, or DRY infrastructure structure.gpt-5.3-codex-spark
windows-infra-admin—Use when a task needs Windows infrastructure administration across Active Directory, DNS, DHCP, GPO, or Windows automation.gpt-5.4
README.md
written by Forgecat
03. Infrastructure
Infrastructure-focused agents for deployment, containerization, orchestration, and IaC work.
azure-infra-engineer — Use when a task needs Azure-specific infrastructure review or implementation across resources, networking, identity, or automation. gpt-5.4Infrastructure
cloud-architect — Use when a task needs cloud architecture review across compute, storage, networking, reliability, or multi-service design. gpt-5.4Infrastructure
database-administrator — Use when a task needs operational database administration review for availability, backups, recovery, permissions, or runtime health. gpt-5.4Infrastructure
deployment-engineer — Use when a task needs deployment workflow changes, release strategy updates, or rollout and rollback safety analysis. gpt-5.4Infrastructure
devops-engineer — Use when a task needs CI, deployment pipeline, release automation, or environment configuration work. gpt-5.4Infrastructure
devops-incident-responder — Use when a task needs rapid operational triage across CI, deployments, infrastructure automation, and service delivery failures. gpt-5.4Infrastructure
docker-expert — Use when a task needs Dockerfile review, image optimization, multi-stage build fixes, or container runtime debugging. gpt-5.3-codex-sparkInfrastructure
incident-responder — Use when a task needs broad production incident triage, containment planning, or evidence-driven root cause analysis. gpt-5.4Infrastructure
kubernetes-specialist — Use when a task needs Kubernetes manifest review, rollout safety analysis, or cluster workload debugging. gpt-5.4Infrastructure
network-engineer — Use when a task needs network-path analysis, service connectivity debugging, load-balancer review, or infrastructure network design input. gpt-5.4Infrastructure
platform-engineer — Use when a task needs internal platform, golden-path, or self-service infrastructure design for developers. gpt-5.4Infrastructure
security-engineer — Use when a task needs infrastructure and platform security engineering across IAM, secrets, network controls, or hardening work. gpt-5.4Infrastructure
sre-engineer — Use when a task needs reliability engineering work involving SLOs, alerting, error budgets, operational safety, or service resilience. gpt-5.4Infrastructure
terraform-engineer — Use when a task needs Terraform module design, plan review, state-aware change analysis, or IaC refactoring. gpt-5.4Infrastructure
terragrunt-expert — Use when a task needs Terragrunt-specific help for module orchestration, environment layering, dependency wiring, or DRY infrastructure structure. gpt-5.3-codex-sparkInfrastructure
windows-infra-admin — Use when a task needs Windows infrastructure administration across Active Directory, DNS, DHCP, GPO, or Windows automation. gpt-5.4Infrastructure
ForgeCat