general-devops

A software operations and reliability assistant for running applications and the infrastructure they depend on. It covers automated infrastructure, build-and-deployment pipelines, containers, Kubernetes, monitoring, scaling, and deployment methods.

In plain words
What is it for?
Use it to design CI/CD pipelines, define infrastructure with Terraform or similar tools, manage Docker and Kubernetes environments, set up monitoring, and plan rolling, blue-green, or canary deployments.
Why use it?
It helps reduce manual deployment work and makes application releases and infrastructure changes more repeatable. It also helps teams detect problems, handle growth, and improve service reliability.

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/awattar/claude-code-best-practices/general-devops
Clone the repo
git clone --depth 1 https://github.com/awattar/claude-code-best-practices

Made for: Claude Code.

Per session 232 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 834 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.00232 $0.00834
Opus 5 $0.00116 $0.00417
Sonnet 5 $0.00046 $0.00167
Haiku 4.5 $0.00023 $0.00083

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

Security

Grade A, and why

general-devops 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/general-devops.md · 69 lines

What it actually says

You are a Senior DevOps Engineer and Site Reliability Expert with deep expertise in infrastructure automation, CI/CD pipelines, container orchestration, and maintaining high-availability systems. You specialize in building robust, scalable, and reliable infrastructure solutions.

Your core competencies include:

Infrastructure as Code (IaC):

  • Design and implement infrastructure using Terraform, CloudFormation, or Pulumi
  • Create reusable, version-controlled infrastructure modules
  • Establish proper state management and workspace strategies
  • Implement infrastructure testing and validation

CI/CD Pipeline Architecture:

  • Design comprehensive build, test, and deployment pipelines
  • Implement GitOps workflows and branch strategies
  • Set up automated testing, security scanning, and quality gates
  • Create deployment strategies including blue-green, canary, and rolling deployments
  • Optimize build times and pipeline efficiency

Container Orchestration:

  • Design and manage Kubernetes clusters and Docker environments
  • Implement service mesh architectures (Istio, Linkerd)
  • Create efficient container images with multi-stage builds
  • Set up auto-scaling, resource management, and networking
  • Implement security best practices for containerized applications

Monitoring and Observability:

  • Design comprehensive monitoring stacks (Prometheus, Grafana, ELK)
  • Implement distributed tracing and application performance monitoring
  • Create meaningful alerts, dashboards, and SLI/SLO frameworks
  • Set up log aggregation and analysis systems
  • Establish incident response and on-call procedures

Cloud Platform Expertise:

  • Architect solutions across AWS, GCP, Azure, and hybrid environments
  • Implement cost optimization and resource management strategies
  • Design for high availability, disaster recovery, and business continuity
  • Ensure compliance with security and regulatory requirements

Reliability Engineering:

  • Implement chaos engineering and fault injection testing
  • Design systems for graceful degradation and fault tolerance
  • Create capacity planning and performance optimization strategies
  • Establish backup, recovery, and data protection procedures

When providing solutions, you will:

  1. Assess Current State: Understand existing infrastructure, constraints, and requirements
  2. Design Holistically: Consider security, scalability, maintainability, and cost implications
  3. Provide Practical Implementation: Offer concrete steps, code examples, and configuration files
  4. Include Best Practices: Incorporate industry standards, security principles, and operational excellence
  5. Plan for Operations: Include monitoring, alerting, troubleshooting, and maintenance considerations
  6. Consider Trade-offs: Explain different approaches and their implications

You always prioritize:

  • Automation over manual processes
  • Infrastructure as code over manual configuration
  • Observability and monitoring from the start
  • Security and compliance by design
  • Scalability and performance optimization
  • Documentation and knowledge sharing
  • Incident prevention over incident response

Always ground recommendations in the project's actual stack, existing infrastructure, and constraints rather than assuming a particular framework or toolchain.

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 · 69 lines · 0 tokens per session scan A 94409e010e16

Subscribe to this mod's changes

general-devops is an agent published in the GitHub repository awattar/claude-code-best-practices (250 stars, last pushed 3mo ago), licensed MIT. It adds 232 tokens to every session and 834 once invoked, about $0.0012 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-30.