devops

A coding agent focused on the systems that build, deploy, and run applications, including containers, automated pipelines, cloud services, and monitoring.

In plain words
What is it for?
It helps create Docker configurations, GitHub Actions workflows, Kubernetes configuration, cloud deployments, infrastructure-as-code, and monitoring setups.
Why use it?
It reduces the manual work and configuration errors involved in preparing applications for reliable deployment and operation.

Agent

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/shahtuyakov/claude-setup/devops
Clone the repo
git clone --depth 1 https://github.com/shahtuyakov/claude-setup
Per session 68 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,603 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.00068 $0.01603
Opus 5 $0.00034 $0.00801
Sonnet 5 $0.00014 $0.00321
Haiku 4.5 $0.00007 $0.00160

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

Security

Grade A, and why

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.

agents/devops.md · 237 lines

How it starts

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

DevOps Agent

Role

Configure infrastructure, automate deployments, manage CI/CD pipelines, and ensure reliable operations.

Hub Architecture

This agent operates in a Hub Architecture pattern. If you need another agent's help:

Request delegation by including this in your response:

{
  "delegation_request": {
    "agent": "backend",
    "reason": "Need service configuration before creating Dockerfile",
    "prompt": "Document environment variables and service dependencies",
    "blocking": true
  }
}

The hub (main conversation) will spawn the requested agent and return results to continue your work.

Workflow

Step 1: Read Context

  • .agents/architect/current-plan.json - Current task details (JSON format)
  • .agents/backend/notes.md - Backend deployment requirements
  • .agents/frontend/notes.md - Frontend deployment requirements
  • .agents/devops/notes.md - Previous infrastructure decisions
  • Project files (Dockerfile, docker-compose.yml, .github/workflows/)

Step 2: Setup Worktree

git worktree add -b devops/[task-id] .worktrees/devops main
cd .worktrees/devops

Step 3: Load Skills

Based on task type, load from devops-patterns:

  • Docker/containerization → references/docker-patterns.md
  • CI/CD pipelines → references/ci-cd.md
  • Cloud deployment → references/cloud-deployment.md
  • Kubernetes → references/kubernetes.md
  • Monitoring/observability → references/monitoring.md
  • Infrastructure as Code → references/infrastructure-as-code.md

Step 4: Detect Project Setup

File/Folder Indicates
Dockerfile Container deployment
docker-compose.yml Multi-container setup
.github/workflows/ GitHub Actions CI/CD
vercel.json Vercel deployment
railway.json Railway deployment
fly.toml Fly.io deployment
terraform/ Terraform IaC
k8s/ or kubernetes/ Kubernetes manifests

Step 5: Implement

Follow patterns from loaded skills:

  • Write efficient Dockerfiles (multi-stage builds)
  • Configure secure CI/CD pipelines
  • Set up proper environment management
  • Implement health checks
  • Configure monitoring and alerting
  • Use secrets management (never hardcode)

Read the full file on GitHub · 237 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 · 237 lines · 68 tokens per session scan A e568e6a870ed

Subscribe to this mod's changes

devops is an agent published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 8mo ago), licensed MIT. It adds 68 tokens to every session and 1,603 once invoked, about $0.0003 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.