DevOps & Infrastructure Claude Code Agents
40 agents in the DevOps & Infrastructure category. Each installs in one command and drops straight into your .claude directory.
Deployment Engineer
"Use this agent when designing, building, or optimizing CI/CD pipelines and deployment automation strategies. Specifically:\\n\\n<example>\\nContext: A team wants to accelerate their release process and reduce deployment friction.\\nuser: \"Our deployments are slow and manual. We deploy every 2 weeks with 4-hour windows. Can you help?\"\\nassistant: \"I'll use the deployment-engineer agent to analyze your current process and implement a modern CI/CD pipeline targeting daily deployments with automated safety checks.\"\\n<commentary>\\nWhen a user needs to design or improve deployment pipelines, increase deployment frequency, or implement CI/CD automation, invoke the deployment-engineer agent to design comprehensive solutions.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Infrastructure team needs to implement safer deployment strategies with minimal downtime.\\nuser: \"We need to roll out features without taking the service down. How do we set up blue-green and canary deployments?\"\\nassistant: \"I'll use the deployment-engineer agent to architect and implement blue-green and canary deployment strategies with automated rollback capabilities and monitoring integration.\"\\n<commentary>\\nWhen the user needs to implement specific deployment strategies like blue-green, canary, or rolling updates with zero-downtime guarantees, use the deployment-engineer agent to design and build the solution.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Organization requires faster incident recovery and rollback capabilities.\\nuser: \"When deployments go wrong, it takes us 45 minutes to recover. We need faster rollbacks.\"\\nassistant: \"I'll use the deployment-engineer agent to design automated rollback procedures, implement health checks, and configure rapid incident response mechanisms to reduce MTTR below 30 minutes.\"\\n<commentary>\\nWhen the focus is on deployment reliability, rollback speed, incident recovery, or meeting DORA metrics (deployment frequency, lead time, MTTR, change failure rate), the deployment-engineer agent is the right choice.\\n</commentary>\\n</example>"
Security Engineer
Security infrastructure and compliance specialist. Use PROACTIVELY for security architecture, compliance frameworks, vulnerability management, security automation, and incident response.
Cloud Architect
"Use this agent when you need to design, evaluate, or optimize cloud infrastructure architecture at scale. Invoke when designing multi-cloud strategies, planning cloud migrations, implementing disaster recovery, optimizing cloud costs, or ensuring security/compliance across cloud platforms. Specifically:\\n\\n<example>\\nContext: A company is planning to migrate their monolithic on-premises application to the cloud and needs architectural guidance.\\nuser: \"We're moving from on-premises to AWS. We have 200 users, need 99.9% uptime, and expect 50% growth annually. What should our architecture look like?\"\\nassistant: \"I'll design a scalable, resilient AWS architecture. Based on your requirements, I recommend a multi-AZ deployment with auto-scaling, RDS for databases with read replicas, CloudFront CDN for static content, and CloudWatch for monitoring. This gives you 99.99% availability, handles 3x traffic spikes, and costs ~40% less than traditional on-premises.\"\\n<commentary>\\nUse the cloud-architect when the user needs to design a complete cloud infrastructure from scratch, especially for migrations. The agent provides comprehensive architecture design covering compute, storage, networking, security, and cost optimization.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An organization is running in AWS but expenses are 60% higher than expected and they need cost optimization without sacrificing performance.\\nuser: \"Our AWS bill jumped to $150K/month. We're using mostly on-demand instances. How do we optimize costs?\"\\nassistant: \"Let me analyze your workloads. I recommend: right-sizing your EC2 instances (typically saves 20-30%), purchasing 3-year Reserved Instances for baseline capacity (40% discount), implementing Spot Instances for fault-tolerant workloads (70% discount), enabling S3 Intelligent-Tiering for storage lifecycle, and using AWS Compute Optimizer. Projected savings: 45-50% or ~$70K/month.\"\\n<commentary>\\nUse the cloud-architect for cost optimization scenarios where existing infrastructure needs financial improvements. The agent applies FinOps practices and cloud-specific cost reduction strategies.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A healthcare provider needs to ensure their multi-cloud infrastructure meets HIPAA compliance and implements proper disaster recovery.\\nuser: \"We use AWS and Azure for redundancy. We need HIPAA compliance and must survive a complete region failure with recovery in under 4 hours.\"\\nassistant: \"I'll design a compliant, resilient architecture. For HIPAA: implement encryption at rest/in-transit, create isolated VPCs with network segmentation, enable CloudTrail/audit logging, implement zero-trust access control. For DR: replicate data across regions in real-time, set up automated failover with RTO < 4 hours, create runbooks, test quarterly. I'll document the architecture and compliance mappings.\"\\n<commentary>\\nUse the cloud-architect when addressing regulatory compliance, disaster recovery requirements, or complex multi-cloud scenarios. The agent designs security-first architectures and business continuity strategies.\\n</commentary>\\n</example>"
Devops Troubleshooter
Production troubleshooting and incident response specialist. Use PROACTIVELY for debugging issues, log analysis, deployment failures, monitoring setup, and root cause analysis.
Network Engineer
"Use this agent when designing, optimizing, or troubleshooting cloud and hybrid network infrastructures, or when addressing network security, performance, or reliability challenges. Specifically:\\n\\n<example>\\nContext: User needs to design a multi-region network for a global application with strict latency and availability requirements.\\nuser: \"We need to design a network that connects our 5 regional data centers with sub-50ms latency and 99.99% uptime. What should the architecture look like?\"\\nassistant: \"I'll use the network-engineer agent to design a multi-region network architecture with proper redundancy, traffic optimization, and failover mechanisms to meet your SLA requirements.\"\\n<commentary>\\nNetwork architecture design for complex infrastructures requires expertise in topology design, redundancy patterns, and performance optimization. This is the primary use case for the network-engineer agent.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User is experiencing network performance issues and needs diagnosis and optimization.\\nuser: \"Our application users in Europe are experiencing 150ms latency to our US-based services. We need to optimize our network routing and consider CDN placement.\"\\nassistant: \"I'll use the network-engineer agent to analyze your current traffic patterns, design a optimized routing strategy, and recommend edge location placement to reduce latency.\"\\n<commentary>\\nPerformance troubleshooting and optimization across distributed networks is a core responsibility of the network-engineer agent.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: User needs to implement security best practices across a cloud infrastructure.\\nuser: \"We're migrating to AWS and need to implement a zero-trust network architecture with proper segmentation, firewall rules, and DDoS protection.\"\\nassistant: \"I'll use the network-engineer agent to design a secure network with micro-segmentation, implement network ACLs, configure WAF rules, and set up DDoS protection mechanisms.\"\\n<commentary>\\nNetwork security implementation including segmentation, access controls, and threat protection requires specialized expertise provided by the network-engineer agent.\\n</commentary>\\n</example>"
Monitoring Specialist
Monitoring and observability infrastructure specialist. Use PROACTIVELY for metrics collection, alerting systems, log aggregation, distributed tracing, SLA monitoring, and performance dashboards.
Terraform Specialist
Terraform and Infrastructure as Code specialist. Use PROACTIVELY for Terraform modules, state management, IaC best practices, provider configurations, workspace management, and drift detection.
Vercel Deployment Specialist
Expert in Vercel platform features, edge functions, middleware, and deployment strategies. Use PROACTIVELY for Vercel deployments, performance optimization, and platform configuration.
Devops Engineer
"Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security. Specifically:\\n\\n<example>\\nContext: A team has repetitive manual infrastructure provisioning processes that take hours and need to migrate to Infrastructure as Code with multiple cloud environments.\\nuser: \"We're manually provisioning servers for dev, staging, and production. It's error-prone and slow. We need to automate this with IaC using Terraform, support AWS and Azure, and ensure consistency across environments.\"\\nassistant: \"I'll architect a comprehensive IaC solution. I'll design modular Terraform modules for compute, networking, storage, and databases. I'll set up multi-environment structures with dev/staging/prod configurations, implement state management, create automated drift detection, and establish GitOps workflows so deployments trigger on code changes. I'll also add security scanning and compliance automation.\"\\n<commentary>\\nUse the devops-engineer agent when implementing Infrastructure as Code, automating infrastructure provisioning, or migrating from manual processes to fully automated, version-controlled infrastructure management.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A development team struggles with slow, unreliable deployments and wants to establish modern CI/CD practices with multiple deployment strategies.\\nuser: \"Our deployments take 2 hours, fail frequently, and have no rollback capability. We need a proper CI/CD pipeline with containerization, automated testing gates, canary deployments, and quick rollbacks.\"\\nassistant: \"I'll design a complete CI/CD transformation. I'll containerize your application with Docker, build an automated pipeline using GitHub Actions or GitLab CI with test automation and security scanning, implement canary and blue-green deployment strategies, set up comprehensive monitoring with automated rollbacks, and create runbooks for incident response. I'll target 10+ deployments per day with sub-30-minute MTTR.\"\\n<commentary>\\nInvoke this agent when establishing or improving CI/CD pipelines, implementing deployment automation, reducing mean time to deployment, and enabling teams to deploy safely and frequently.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Production incidents reveal gaps in monitoring, observability, and incident response processes that delay recovery and create toil for the team.\\nuser: \"We had an outage last week that took 4 hours to detect and 2 hours to resolve. We need better monitoring, alerting, observability, and documented incident response procedures.\"\\nassistant: \"I'll establish production observability and incident response. I'll implement comprehensive metrics collection, centralized logging, distributed tracing, and intelligent alerting with alert routing. I'll create SLOs and error budgets to balance feature velocity with reliability. I'll establish on-call procedures, create runbooks for common incidents, and implement blameless postmortem processes. This will reduce MTTR to under 30 minutes and build a healthy on-call culture.\"\\n<commentary>\\nUse this agent when building monitoring and observability infrastructure, establishing incident response procedures, reducing mean time to resolution, and improving operational reliability and team satisfaction.\\n</commentary>\\n</example>"
Devops Expert
DevOps specialist following the infinity loop principle (Plan → Code → Build → Test → Release → Deploy → Operate → Monitor) with focus on automation, collaboration, and continuous improvement
Kubernetes Specialist
"Use this agent when you need to design, deploy, configure, or troubleshoot Kubernetes clusters and workloads in production environments. Specifically:\\n\\n<example>\\nContext: Your team needs to set up a production Kubernetes cluster with high availability, security hardening, and auto-scaling capabilities.\\nuser: \"We're migrating our microservices to Kubernetes. Can you design a production-grade cluster architecture with security best practices and performance optimization?\"\\nassistant: \"I'll design a multi-master control plane setup with etcd redundancy, implement CIS Kubernetes Benchmark compliance, configure RBAC and network policies, set up auto-scaling policies, and create a disaster recovery plan with tested failover procedures.\"\\n<commentary>\\nUse the kubernetes-specialist when designing new Kubernetes infrastructure from scratch, especially when production requirements include high availability, security compliance, and scalability targets.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An existing Kubernetes cluster has performance issues and security gaps that need remediation.\\nuser: \"Our Kubernetes cluster is using 40% of its CPU capacity but has frequent pod evictions. Performance is degraded and we're not confident in our security posture. Can you audit and optimize?\"\\nassistant: \"I'll analyze your cluster configuration, review resource requests/limits, check for security vulnerabilities, implement node affinity rules, enable cluster autoscaling, and recommend storage and networking optimizations to improve efficiency while maintaining security.\"\\n<commentary>\\nUse the kubernetes-specialist when troubleshooting cluster performance issues, security problems, or resource inefficiencies in existing environments. The agent performs diagnostics and implements targeted improvements.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Your organization is adopting multi-tenancy with multiple teams sharing a single Kubernetes cluster.\\nuser: \"We need to set up namespace isolation, separate resource quotas, and ensure teams can't access each other's data. Also need network segmentation and audit logging.\"\\nassistant: \"I'll configure namespace-based isolation with RBAC per tenant, implement resource quotas and network policies, set up persistent volume access controls, enable audit logging with tenant filtering, and create GitOps workflows for multi-tenant management.\"\\n<commentary>\\nUse the kubernetes-specialist when implementing multi-tenancy, complex networking requirements, or setting up GitOps workflows like ArgoCD. These scenarios require deep Kubernetes expertise for production safety.\\n</commentary>\\n</example>"
Microservices Architect
"Use when designing distributed system architecture, decomposing monolithic applications into independent microservices, or establishing communication patterns between services at scale. Specifically:\\n\\n<example>\\nContext: A company has a monolithic e-commerce application becoming difficult to scale and deploy. Different teams need to own separate business domains independently.\\nuser: \"Help us decompose our monolith into microservices. We have user management, product catalog, orders, and payments all tightly coupled. What's the best way to split this?\"\\nassistant: \"I'll help you decompose using domain-driven design. First, let's identify bounded contexts: Users, Products, Orders, and Payments are clear domains. For service boundaries, I'd recommend: 1) User Service (authentication, profiles), 2) Product Service (catalog, inventory), 3) Order Service (orchestration, shipping), 4) Payment Service (processing, reconciliation). For data strategy, each service gets its own database. Orders needs events (OrderCreated, PaymentProcessed) published to Kafka. I'll create the architecture diagram, database schemas, and deployment manifests.\"\\n<commentary>\\nUse this agent when facing monolith decomposition challenges or when establishing the initial microservices architecture. The agent excels at domain analysis, service boundary identification, and creating the foundational structure for distributed systems.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Multiple teams are building microservices that need to communicate. Some services need real-time responses while others can process asynchronously. Performance and failure resilience are critical requirements.\\nuser: \"We have 8 microservices that need to talk to each other. How should we handle synchronous calls like user service to order service, and asynchronous workflows like order to payment to fulfillment?\"\\nassistant: \"I'll design a hybrid communication strategy: For tight coupling (user→order), use gRPC with circuit breakers and timeouts for low-latency sync calls. For loose coupling (order→payment→fulfillment), use Kafka event streaming with saga pattern for distributed transactions. I'll implement resilience patterns: exponential backoff retries, bulkhead isolation per service, and health checks. Here's the service mesh config for Istio to manage traffic, retries, and timeouts automatically.\"\\n<commentary>\\nUse this agent for complex inter-service communication design, especially when balancing synchronous and asynchronous patterns. The agent designs resilience patterns, message architectures, and service mesh configurations that production systems require.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A microservices platform has been running for 6 months but operational issues are emerging: cascading failures, deployment coordination problems, observability gaps, and unclear service ownership.\\nuser: \"Our microservices are live but we're struggling with production reliability. We need better monitoring, clearer ownership models, and ways to prevent one service failure from crashing everything.\"\\nassistant: \"I'll design operational excellence across three areas: 1) Resilience: implement circuit breakers, distributed tracing via Jaeger, and chaos engineering tests to find failure modes. 2) Ownership: create clear service ownership model with on-call rotations, runbooks, and SLI/SLO definitions per service. 3) Observability: deploy Prometheus for metrics, ELK for logs, and correlation IDs for tracing request flows across services. I'll also establish deployment procedures with canary releases and automated rollback triggers.\"\\n<commentary>\\nUse this agent when implementing production hardening for existing microservices platforms. The agent focuses on operational excellence: resilience patterns, team structures, observability, and deployment strategies that mature distributed systems need.\\n</commentary>\\n</example>"
Incident Responder
"Use this agent when an active security breach, service outage, or operational incident requires immediate response, evidence preservation, and coordinated recovery. Specifically:\\n\\n<example>\\nContext: Your production database has gone offline and customers are experiencing service failures.\\nuser: \"Our database is down and affecting all users. We need to respond immediately.\"\\nassistant: \"I'll activate the incident-responder agent to manage this service outage - we'll assess severity, mobilize the response team, preserve evidence, coordinate communication, and execute recovery.\"\\n<commentary>\\nWhen a critical operational incident occurs (service outage, performance degradation, data loss), use incident-responder to coordinate rapid response, investigation, and recovery with proper stakeholder communication.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Your security team has detected suspicious login activity and potential unauthorized data access.\\nuser: \"We may have been compromised. Unusual login patterns detected in the audit logs from last night.\"\\nassistant: \"I'll engage the incident-responder agent to handle this security incident - we'll conduct forensic analysis, assess the scope of compromise, contain the threat, and follow proper notification procedures.\"\\n<commentary>\\nWhen a security breach or suspicious activity is discovered, use incident-responder to investigate thoroughly, collect forensic evidence, determine impact, and coordinate response with legal and compliance teams.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A production incident has been resolved and you need to conduct a post-incident review.\\nuser: \"The system is back up. Now we need to document what happened and prevent this in the future.\"\\nassistant: \"I'll use the incident-responder agent to facilitate the post-incident review - analyzing logs, documenting the timeline, identifying root causes, and recommending process improvements.\"\\n<commentary>\\nAfter an incident is resolved, use incident-responder to conduct comprehensive post-incident analysis, create detailed documentation, extract lessons learned, and implement preventive measures.\\n</commentary>\\n</example>"
Sre Engineer
"Use this agent when you need to establish or improve system reliability through SLO definition, error budget management, and automation. Invoke when implementing SLI/SLO frameworks, reducing operational toil, designing fault-tolerant systems, conducting chaos engineering, or optimizing incident response processes. Specifically:\\n\\n<example>\\nContext: A rapidly growing SaaS platform is experiencing frequent outages and lacks formal reliability targets. The team is spending 60% of their time on operational toil.\\nuser: \"Our service goes down monthly, and on-call is burning people out. We don't have clear reliability targets. How do we establish reliability practices?\"\\nassistant: \"I'll establish an SRE framework for your platform. First, let's define SLIs for user-facing requests (latency, error rate, availability). Based on your criticality, I recommend 99.95% SLO with a 0.72% monthly error budget. We'll implement error budget policies: feature development pauses when budget burns > 5%/day. For toil reduction, I'll audit your incidents to identify automation opportunities—likely target: reduce toil from 60% to 30% in 3 months. I'll design monitoring, runbooks, and chaos tests to validate resilience. This prevents burnout while maintaining velocity.\"\\n<commentary>\\nUse the sre-engineer when establishing SRE practices from scratch or transforming a reactive on-call culture into a data-driven reliability program. The agent designs comprehensive SLI/SLO frameworks and error budget policies.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A company has defined SLOs but is consistently missing them. They want to understand what's driving violations and how to improve.\\nuser: \"Our SLO is 99.9% but we're hitting 99.2%. We don't know why. Incidents are unpredictable and recovery is slow. MTTR is 45 minutes.\"\\nassistant: \"Let me analyze your reliability posture. I'll review your incident history to identify patterns—common causes usually cluster around 3-4 areas. Based on typical profiles, I'll recommend: 1) Implement circuit breakers in your critical services to prevent cascading failures, 2) Set up automated playbooks for your top 5 incident types to reduce MTTR from 45 min to < 15 min, 3) Design chaos experiments targeting your weakest dependencies, 4) Establish SLO review meetings to track burn rate weekly. This typically improves SLO compliance to 99.8+% within 60 days.\"\\n<commentary>\\nUse the sre-engineer when the organization has SLOs defined but can't meet them consistently. The agent performs root cause analysis and designs targeted reliability improvements through automation and architectural changes.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A critical infrastructure team needs to scale their system to handle 10x traffic while maintaining reliability and managing costs during growth.\\nuser: \"We're growing 100% YoY and need to handle 10x traffic in 6 months. Current costs are $200K/month. How do we scale without breaking reliability or tripling our bill?\"\\nassistant: \"I'll design a resilient, cost-optimized architecture for hypergrowth. First, I'll forecast capacity needs using your growth curve and design auto-scaling with predictive policies. For reliability: implement redundancy across availability zones, design graceful degradation to shed non-critical load, and set up chaos testing for failure scenarios. For cost: right-size your infrastructure, use spot instances for non-critical workloads (save ~60%), implement resource quotas. I'll also establish a capacity planning process to prevent surprises. Projected outcome: handle 10x traffic at ~80% of current per-unit costs while maintaining 99.95% SLO.\"\\n<commentary>\\nUse the sre-engineer when the organization faces significant infrastructure changes like hypergrowth, major migrations, or major architecture shifts. The agent balances reliability, cost, and performance during transformation.\\n</commentary>\\n</example>"
Terraform Engineer
"Use when building, refactoring, or scaling infrastructure as code using Terraform with focus on multi-cloud deployments, module architecture, and enterprise-grade state management. Specifically:\\n\\n<example>\\nContext: Team needs to migrate AWS infrastructure from manual console provisioning to reusable Terraform modules for cost tracking and consistency.\\nuser: \"We have 50+ AWS resources scattered across three environments with no version control. Need to convert this to Terraform modules with proper state management and environments.\"\\nassistant: \"I'll analyze your current resources, design a modular architecture with environment-specific configurations, implement remote state with locking, and create reusable modules for compute, networking, and databases. This enables infrastructure versioning, cost attribution per environment, and safe CI/CD deployments with plan/apply approval gates.\"\\n<commentary>\\nThis agent should be invoked when existing infrastructure needs to be converted to IaC with proper modularity and state management. The agent's expertise in multi-environment variable management, state locking, and module composition directly addresses this use case.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Platform team building internal developer platform needs reusable Terraform modules for RDS, VPC, and ECS that multiple teams can consume with different configurations.\\nuser: \"We need 5 reusable Terraform modules for common infrastructure components. Teams will consume these through module registry with version constraints.\"\\nassistant: \"I'll design composable modules with clear input/output contracts, implement variable validation, add comprehensive documentation, set up semantic versioning, and create examples for each module. Each module will support multiple configurations while maintaining security standards and cost tracking through resource tagging.\"\\n<commentary>\\nInvoke this agent when you need to develop a library of reusable infrastructure modules with version management and clear contracts. The agent specializes in module composition patterns, documentation standards, and enforcing best practices across a module registry.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: DevOps team needs to implement policy-as-code scanning for Terraform, cost estimation, and automated security compliance checks in their CI/CD pipeline.\\nuser: \"We want to add security scanning, cost estimation, and compliance checks to our Terraform CI/CD pipeline before apply. Need integration with our GitHub workflows.\"\\nassistant: \"I'll implement OPA/Sentinel policies for security and compliance scanning, integrate cost estimation tools, set up automated plan/apply workflows with approval gates, enable state locking for safety, and create runbooks for disaster recovery. All scanning results and cost projections will be posted to pull requests for review.\"\\n<commentary>\\nUse this agent when you need to establish CI/CD automation around Terraform with security scanning, cost controls, and approval workflows. The agent excels at implementing governance frameworks and enterprise deployment patterns that prevent drift and ensure compliance.\\n</commentary>\\n</example>"
Platform Engineer
"Use when building or improving internal developer platforms (IDPs), designing self-service infrastructure, or optimizing developer workflows to reduce friction and accelerate delivery. The platform-engineer agent specializes in designing platform architecture, implementing golden paths, and maximizing developer self-service capabilities. Specifically:\\n\\n<example>\\nContext: A team struggles with manual environment provisioning that takes 2 weeks and bottlenecks their release cycle. They need a self-service platform.\\nuser: \"Our teams are manually provisioning environments and it's slowing us down. We need a better solution.\"\\nassistant: \"I'll use the platform-engineer agent to design a self-service environment provisioning platform with golden paths that reduces setup from 2 weeks to minutes, including Backstage portal integration and GitOps workflows.\"\\n<commentary>\\nUse the platform-engineer agent when the goal is to build self-service infrastructure that reduces manual toil and improves developer velocity. This agent designs the complete platform architecture, not just individual services.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A company has multiple infrastructure tools scattered across different platforms with poor discoverability. They want a unified developer experience.\\nuser: \"Developers are confused about which tools to use. We need a centralized platform and API layer.\"\\nassistant: \"I'll engage the platform-engineer agent to design a comprehensive developer platform with a Backstage service catalog, unified APIs, and golden path templates for common workflows.\"\\n<commentary>\\nWhen you need to improve developer experience across an organization by creating unified abstractions and reducing cognitive load, invoke the platform-engineer agent to design the platform architecture and adoption strategy.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An organization wants to standardize how teams deploy services and ensure compliance across deployments using GitOps.\\nuser: \"We need to ensure all teams follow the same deployment process and security policies.\"\\nassistant: \"I'll use the platform-engineer agent to implement a GitOps-based platform with golden path templates, policy enforcement, and automated compliance validation.\"\\n<commentary>\\nUse the platform-engineer agent when you need to design scalable, policy-driven infrastructure abstractions that enforce standards while maintaining flexibility. This includes GitOps workflows, approval processes, and compliance automation.\\n</commentary>\\n</example>"
Windows Infra Admin
"Use when managing Windows Server infrastructure, Active Directory, DNS, DHCP, and Group Policy configurations, especially for enterprise-scale deployments requiring safe automation and compliance validation. Specifically:\\n\\n<example>\\nContext: Organization needs to migrate 500+ user accounts and computer objects from one Active Directory domain to another with minimal downtime and no data loss.\\nuser: \"We're consolidating domains and need to move 500 users and 200 computers safely. Can you automate this with pre-migration validation and rollback capability?\"\\nassistant: \"I'll design a phased migration workflow with pre-flight checks (trust relationships, replication status, object dependencies), create export/backup scripts, execute staged migrations by OU with validation at each phase, implement post-migration verification, and document rollback procedures. Testing will use a pilot group first.\"\\n<commentary>\\nInvoke this agent for large-scale Active Directory changes requiring pre-change verification, detailed planning, and rollback paths. The agent specializes in safe change engineering with impact assessments.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Enterprise has 10 DNS zones with thousands of records across multiple servers and needs to audit, clean up scavenging settings, and document configurations for compliance.\\nuser: \"Our DNS infrastructure is undocumented and we suspect stale records. Can you audit all zones, identify issues, and create a cleanup plan with rollback documentation?\"\\nassistant: \"I'll enumerate all DNS zones and records across your servers, check scavenging policies and timestamps, identify potential stale entries, create cleanup scripts with WhatIf previews, export configurations for backup, and generate compliance documentation showing record counts, last-modified dates, and zone health.\"\\n<commentary>\\nUse this agent when auditing Windows DNS/DHCP infrastructure, planning cleanup operations, or documenting configurations for compliance. The agent excels at pre-change validation and detailed reporting.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Team needs to enforce standardized security settings across 50 Group Policy Objects in a large forest with multiple domains.\\nuser: \"We need to link 20 new security GPOs to OUs across three domains, validate the assignments, and measure impact with WMI filters. How do we do this safely?\"\\nassistant: \"I'll create the GPOs with security baselines, map OU structures to identify correct linking targets, implement WMI filters for targeted application, preview changes with targeted scope analysis, generate before/after reports showing which computers will receive settings, and provide rollback procedures if needed.\"\\n<commentary>\\nInvoke this agent when deploying complex Group Policy changes, bulk relinking operations, or GPO migrations. The agent provides impact analysis and safe deployment with validation at each step.\\n</commentary>\\n</example>"
Apify Integration Expert
Expert agent for integrating Apify Actors into codebases. Handles Actor selection, workflow design, implementation across JavaScript/TypeScript and Python, testing, and production-ready deployment. Use proactively whenever the user wants to scrape a website, automate a browser task, or wire an Apify Actor into their app.
Devops Incident Responder
"Use when actively responding to production incidents, diagnosing critical service failures, or conducting incident postmortems to implement permanent fixes and preventative measures. Specifically:\\n\\n<example>\\nContext: A critical database service has gone down, causing customer-facing API timeouts. The on-call engineer needs immediate help triaging impact and determining next steps.\\nuser: \"We're getting spiked error rates on our API - database connection timeouts appearing 2 minutes ago. I need to triage this quickly.\"\\nassistant: \"I'll help diagnose this immediately. Let me query the system architecture and recent changes, check database logs for connection issues, identify affected services, assess customer impact, and determine if rollback or failover is needed. Do we have a distributed trace showing the failure pattern?\"\\n<commentary>\\nUse the devops-incident-responder when actively in incident response mode needing rapid diagnosis and decision support during an active production incident.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: An incident occurred 12 hours ago and was resolved, but the team needs to conduct a thorough postmortem to prevent recurrence.\\nuser: \"We had a deployment issue this morning that caused 30 minutes of downtime. Can you help us document the timeline and identify what we could have prevented?\"\\nassistant: \"I'll help conduct the postmortem. Let me gather the timeline from logs, analyze the root cause through the incident sequence, identify preventative measures we could have implemented, and create action items for our runbook and monitoring gaps. I'll structure this in a blameless format focused on system improvements.\"\\n<commentary>\\nUse the devops-incident-responder for post-incident analysis and creating improvements to prevent similar failures, focusing on root cause analysis and process refinement.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: The engineering team wants to improve their incident detection and response capabilities to reduce MTTR and runbook coverage gaps.\\nuser: \"Our MTTR is currently 45 minutes and we only have runbooks for 60% of critical scenarios. What should we focus on first?\"\\nassistant: \"I'll assess your current incident readiness. Let me review your monitoring coverage, alert effectiveness, existing runbooks, team procedures, and historical incidents. I'll identify gaps in detection speed, recommend alert optimization, create runbook templates for missing procedures, and suggest automation opportunities to reduce MTTR.\"\\n<commentary>\\nUse the devops-incident-responder when building or improving incident response infrastructure, implementing runbooks, alert optimization, and automation systems to reduce incident impact.\\n</commentary>\\n</example>"
Terragrunt Expert
Expert Terragrunt specialist mastering infrastructure orchestration, DRY configurations, and multi-environment deployments. Masters stacks, units, dependency management, and scalable IaC patterns with focus on code reuse, maintainability, and enterprise-grade infrastructure automation.
Azure Principal Architect
Provide expert Azure Principal Architect guidance using Azure Well-Architected Framework principles and Microsoft best practices.
Azure Saas Architect
Provide expert Azure SaaS Architect guidance focusing on multitenant applications using Azure Well-Architected SaaS principles and Microsoft best practices.
Azure Infra Engineer
"Use when designing, deploying, or managing Azure infrastructure with focus on network architecture, Entra ID integration, PowerShell automation, and Bicep IaC. Specifically:\\n\\n<example>\\nContext: Building a multi-region Azure infrastructure with hybrid identity and secure networking for an enterprise migration\\nuser: \"We're migrating on-premises workloads to Azure. Need multi-region infrastructure with VNets, NSGs, Azure Firewall, Entra ID sync with on-prem AD, managed identities for applications, and everything automated with PowerShell and Bicep templates.\"\\nassistant: \"I'll design and implement: multi-region VNet architecture with hub-spoke topology, Azure Firewall for centralized security, NSG rules with least-privilege access, Entra ID Connect configuration for hybrid identity, managed identities for service principals, comprehensive Bicep templates for infrastructure-as-code, PowerShell scripts for deployment and ongoing management, RBAC policies aligned with your AD groups, and monitoring/alerting for all resources.\"\\n<commentary>\\nUse azure-infra-engineer when you need to design complete Azure network infrastructure, integrate on-premises identity systems (Entra ID), automate deployments with PowerShell and Bicep, or manage complex multi-region Azure environments. This agent specializes in the infrastructure layer and operational automation that azure-specialist/cloud-architect don't dive into.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Converting manual Azure deployments to infrastructure-as-code with Bicep and automating operational tasks with PowerShell\\nuser: \"Our Azure infrastructure is created manually through the portal and undocumented. We have VMs, storage, networking, all done manually. How do we convert to Bicep, version control it, automate deployments, and ensure consistency across dev/test/prod?\"\\nassistant: \"I'll create a Bicep-based IaC strategy: map existing resources, write modular Bicep templates for compute/network/storage/security, set up parameter files for different environments, create PowerShell deployment scripts with pre-flight validation, establish naming standards and tagging strategy, implement resource group organization, set up CI/CD pipelines for Bicep validation and deployment, document architecture decisions, and train your team on maintaining IaC.\"\\n<commentary>\\nInvoke azure-infra-engineer when modernizing from manual Azure deployments to infrastructure-as-code, implementing Bicep templates, automating operational tasks with PowerShell, or establishing IaC governance and best practices for your Azure subscriptions.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Troubleshooting Azure networking issues and implementing security policies for compliance\\nuser: \"VMs can't reach on-premises databases through our site-to-site VPN. We need to debug VNet routing, NSG rules, Azure Firewall policies, and implement zero-trust principles with managed identities. Also need to audit access with Azure Policies.\"\\nassistant: \"I'll diagnose and fix: check VNet peering and routing tables with PowerShell, validate NSG rules on subnets/NICs, test Azure Firewall rules and diagnostics, fix VPN gateway configuration, implement user-defined routes (UDRs), set up managed identities for all services eliminating shared secrets, apply Azure Policy for zero-trust enforcement, audit RBAC assignments, and create runbooks for monitoring connectivity and enforcing compliance automatically.\"\\n<commentary>\\nUse azure-infra-engineer for Azure networking troubleshooting, security policy implementation, VPN/ExpressRoute configuration, identity and access management (Entra ID, managed identities, RBAC), or compliance automation with Azure Policies and PowerShell operational scripts.\\n</commentary>\\n</example>"
Azure Verified Modules Terraform
Create, update, or review Azure IaC in Terraform using Azure Verified Modules (AVM).
Se Gitops Ci Specialist
DevOps specialist for CI/CD pipelines, deployment debugging, and GitOps workflows focused on making deployments boring and reliable
Terraform Iac Reviewer
Terraform-focused agent that reviews and creates safer IaC changes with emphasis on state safety, least privilege, module patterns, drift detection, and plan/apply discipline
Azure Logic Apps Expert
Expert guidance for Azure Logic Apps development focusing on workflow design, integration patterns, and JSON-based Workflow Definition Language.
Bicep Implement
Act as an Azure Bicep Infrastructure as Code coding specialist that creates Bicep templates.
Kusto Assistant
Expert KQL assistant for live Azure Data Explorer analysis via Azure MCP server
Microsoft Study Mode
Activate your personal Microsoft/Azure tutor - learn through guided discovery, not just answers.
Neo4j Docker Client Generator
AI agent that generates simple, high-quality Python Neo4j client libraries from GitHub issues with proper best practices
Arm Migration
Arm Cloud Migration Assistant accelerates moving x86 workloads to Arm infrastructure. It scans the repository for architecture assumptions, portability issues, container base image and dependency incompatibilities, and recommends Arm-optimized changes. It can drive multi-arch container builds, validate performance, and guide optimization, enabling smooth cross-platform deployment directly inside GitHub.
Azure Iac Exporter
Export existing Azure resources to Infrastructure as Code templates via Azure Resource Graph analysis, Azure Resource Manager API calls, and azure-iac-generator integration. Use this skill when the user asks to export, convert, migrate, or extract existing Azure resources to IaC templates (Bicep, ARM Templates, Terraform, Pulumi).
Terraform Azure Implement
Act as an Azure Terraform Infrastructure as Code coding specialist that creates and reviews Terraform for Azure resources.
Terraform Azure Planning
Act as implementation planner for your Azure Terraform Infrastructure as Code task.
Azure Iac Generator
Central hub for generating Infrastructure as Code (Bicep, ARM, Terraform, Pulumi) with format-specific validation and best practices. Use this skill when the user asks to generate, create, write, or build infrastructure code, deployment code, or IaC templates in any format (Bicep, ARM Templates, Terraform, Pulumi).
Azure Verified Modules Bicep
Create, update, or review Azure IaC in Bicep using Azure Verified Modules (AVM).
M365 Admin
"Use when automating Microsoft 365 administrative tasks including Exchange Online mailbox provisioning, Teams collaboration management, SharePoint site configuration, license lifecycle management, and Graph API-driven identity automation. Specifically:\\n\\n<example>\\nContext: Enterprise onboarding new employees across departments with Exchange mailbox creation, Teams team membership, SharePoint site permissions, and license assignment\\nuser: \"We need to automate onboarding so when a new employee is added to our HR system, they automatically get an Exchange mailbox with forwarding rules, added to their department's Teams channel, granted appropriate SharePoint site permissions, and assigned the correct M365 licenses based on their role.\"\\nassistant: \"I'll create a comprehensive onboarding automation workflow: Connect to Exchange Online to provision mailbox with specific retention/forwarding settings, use Microsoft Graph to create/manage Teams membership and channel assignments, configure SharePoint site access with least-privilege permissions based on department, implement license assignment logic using Graph API to apply correct SKUs, add audit logging for compliance, handle error conditions with notifications, and provide a deployment guide with required permissions.\"\\n<commentary>\\nUse m365-admin for building enterprise-scale onboarding automation across multiple M365 workloads where you need coordinated provisioning, license management via Graph API, and security controls to ensure proper access governance.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Auditing and fixing external sharing misconfigurations across SharePoint and Teams before security audit\\nuser: \"Our security team found excessive external sharing in SharePoint sites and Teams channels. We need to audit all external sharing, identify misconfigured sites, disable inappropriate external access, and implement policies to prevent future issues.\"\\nassistant: \"I'll build an audit and remediation solution: Query SharePoint sites via Graph API to enumerate external sharing policies and site permissions, list Teams external guest access settings, generate a detailed report of high-risk external shares, create PowerShell scripts to disable external sharing where needed, implement SharePoint information barriers and Teams external access policies, set up ongoing monitoring with alerts for unauthorized external sharing attempts.\"\\n<commentary>\\nInvoke m365-admin when you need to audit M365 security posture across Exchange, Teams, and SharePoint, remediate access misconfigurations, implement compliance policies, or prevent unauthorized external collaboration.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Bulk mailbox migration with retention policy changes and compliance holds\\nuser: \"We're consolidating from multiple Exchange organizations into a single tenant. Need to migrate 5,000 mailboxes while applying new retention policies, implementing eDiscovery holds for legal compliance, and updating transport rules for the merged organization.\"\\nassistant: \"I'll orchestrate the migration: Create Exchange transport rules for the consolidated domain, prepare mailbox provisioning and archive configuration using Exchange Online commands, implement retention and holds policies via Compliance Center API, validate migration waves with PowerShell batching, set up mailbox forwarding for cutover period, audit user data integrity post-migration, configure compliance holds for specified users, and create monitoring dashboards for migration progress and issues.\"\\n<commentary>\\nUse m365-admin for complex Exchange Online migrations, bulk mailbox operations, retention policy implementations, compliance/legal holds, or when coordinating configuration changes across a large M365 tenant.\\n</commentary>\\n</example>"
Bicep Plan
Act as implementation planner for your Azure Bicep Infrastructure as Code task.
Octopus Deploy Release Notes Mcp
Generates markdown release notes for an Octopus Deploy release by combining Octopus release/build-information data with commit details (message, author, date, diff) fetched from GitHub. Use when a user asks for release notes, a changelog, or a deployment summary for a specific Octopus Deploy project, environment, or space. Requires the Octopus Deploy MCP server and the GitHub MCP server to be configured.
Other Agents Categories
Catalog data and component content are sourced from the open-source davila7/claude-code-templates project (MIT license). ToolZip curates the listing and writes original descriptions; every component links back to its original source. Claude Code is a product of Anthropic. ToolZip is an independent catalog and is not affiliated with or endorsed by Anthropic.