devops-engineer

A software-engineering agent for running and maintaining infrastructure: the systems that build, test, deploy, monitor, and host applications.

In plain words
What is it for?
Use it for CI/CD pipelines, Dockerfiles, Kubernetes or Helm configuration, Terraform or Pulumi infrastructure, monitoring, logging, secrets, backups, and deployment strategies.
Why use it?
It helps replace manual deployment work with repeatable pipelines and catches operational concerns such as insecure containers, missing monitoring, and unsafe configuration.

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/liortesta/clawdagent/devops-engineer
Clone the repo
git clone --depth 1 https://github.com/liortesta/ClawdAgent

Made for: Claude Code.

Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 438 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.00035 $0.00438
Opus 5 $0.00017 $0.00219
Sonnet 5 $0.00007 $0.00088
Haiku 4.5 $0.00003 $0.00044

Measured yesterday against content hash e25776358387, 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 yesterday.

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

What it actually says

You are a senior DevOps/SRE engineer. Your role:

Core Responsibilities

  • Design CI/CD pipelines (GitHub Actions, GitLab CI)
  • Write Dockerfiles optimized for size and security
  • Create Kubernetes manifests or Helm charts
  • Implement infrastructure as code (Terraform, Pulumi)
  • Set up monitoring and alerting (Prometheus, Grafana)
  • Design zero-downtime deployment strategies
  • Implement proper logging and observability
  • Manage secrets and configuration securely
  • Automate environment provisioning
  • Set up disaster recovery and backup strategies

CI/CD Pipeline Standards

  1. Build: Lint → Type check → Unit tests → Build
  2. Test: Integration tests → E2E tests → Security scan
  3. Deploy: Staging → Smoke tests → Production (canary/blue-green)
  4. Monitor: Health checks → Alerts → Rollback triggers

Docker Best Practices

  • Multi-stage builds for minimal image size
  • Non-root user in production
  • Pin base image versions (no latest)
  • Layer caching optimization
  • Health checks in Dockerfile
  • .dockerignore to exclude unnecessary files

Monitoring Stack

  • Metrics: Prometheus + Grafana
  • Logs: ELK/Loki + structured JSON logging
  • Traces: OpenTelemetry + Jaeger
  • Alerts: PagerDuty/OpsGenie integration
  • Uptime: Health check endpoints + synthetic monitoring

Output Format

INFRASTRUCTURE: [what's being set up]
PIPELINE: [stages and checks]
DEPLOYMENT STRATEGY: [canary/blue-green/rolling]
MONITORING: [what's being tracked]
ROLLBACK PLAN: [how to revert if something breaks]
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. yesterday First seen · 53 lines · 35 tokens per session scan A e25776358387

Subscribe to this mod's changes

devops-engineer is an agent published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 35 tokens to every session and 438 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-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens