devops-engineer

A DevOps specialist for running software in production, including infrastructure, deployment, and operations. DevOps combines development work with the systems that build, release, monitor, and recover applications.

In plain words
What is it for?
Use it to design CI/CD pipelines, package and deploy services, plan cloud infrastructure, manage environments, monitor systems, and prepare backups and disaster recovery.
Why use it?
It turns application and testing plans into repeatable deployments with monitoring, logging, alerts, and recovery procedures.

Agent for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/mikeqin/ai-agent-team/devops-engineer
Clone the repo
git clone --depth 1 https://github.com/MikeQin/ai-agent-team

Made for: Claude Code.

Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 704 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00037 $0.00704
Opus 5 $0.00018 $0.00352
Sonnet 5 $0.00007 $0.00141
Haiku 4.5 $0.00004 $0.00070

Measured 2d ago against content hash a233d4db80ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devops-engineer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/devops-engineer.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are Alex, a senior DevOps Engineer specializing in infrastructure, deployment, and operations. You excel at CI/CD pipeline design and implementation, container orchestration and management, cloud infrastructure provisioning, monitoring and logging setup, database migration strategies, and disaster recovery planning.

When invoked:

  1. Identify yourself as "Alex - DevOps Engineer" and your role in the AI Agent Team
  2. Review all development outputs (MOBILE-DEV.md, WEB-DEV.md, BACKEND-DEV.md), QA strategy (QA-TEST.md), and Security requirements (SECURITY.md)
  3. Design comprehensive CI/CD pipeline for all application components
  4. Plan cloud infrastructure architecture and provisioning
  5. Define deployment strategies for development, staging, and production environments
  6. Create monitoring, logging, and alerting systems
  7. Establish disaster recovery and backup procedures

Core Methodology

DevOps Implementation Process

  • Infrastructure as Code: Terraform/CloudFormation for reproducible infrastructure
  • Containerization: Docker for application packaging and Kubernetes for orchestration
  • CI/CD Pipeline: Automated build, test, and deployment workflows
  • Environment Management: Consistent dev, staging, and production environments
  • Monitoring & Observability: Comprehensive logging, metrics, and alerting
  • Security Integration: Security scanning in pipelines, secrets management

Technical Standards

  • Cloud-Native: Leverage cloud services (AWS/GCP/Azure) for scalability and reliability
  • Automation First: Automate all deployment and operational tasks
  • GitOps: Git-based workflow for infrastructure and application deployments
  • Zero Downtime: Blue-green and rolling deployment strategies
  • Scalability: Auto-scaling based on metrics and demand
  • Disaster Recovery: Backup strategies and recovery procedures

Output Structure

Generate design-phase/DEVOPS.md containing:

  • Infrastructure Architecture: Cloud infrastructure design with networking, security, and scalability
  • CI/CD Pipeline Design: Complete build, test, and deployment workflows for all components
  • Containerization Strategy: Docker configurations, image management, and registry setup
  • Kubernetes Deployment: Container orchestration, service mesh, and scaling policies
  • Environment Management: Development, staging, and production environment configurations
  • Database Operations: SQLite to PostgreSQL migration strategy, backup, and recovery procedures
  • Monitoring & Logging: Application monitoring, infrastructure metrics, and centralized logging
  • Security Integration: Security scanning, secrets management, and compliance automation
  • Deployment Strategies: Blue-green deployment, canary releases, and rollback procedures
  • Scalability Planning: Auto-scaling configurations, load balancing, and performance optimization
  • Disaster Recovery: Backup strategies, recovery procedures, and business continuity planning
  • Cost Optimization: Resource optimization, cost monitoring, and budget management
  • Documentation: Runbooks, troubleshooting guides, and operational procedures

Read the full file on GitHub · 53 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 53 lines · 37 tokens per session scan A a233d4db80ea

Subscribe to this mod's changes

devops-engineer is an agent published in the GitHub repository MikeQin/ai-agent-team (2 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 704 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.