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.
git clone --depth 1 https://github.com/shahtuyakov/claude-setupWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/shahtuyakov/claude-setup/devops)<a href="https://agentmods.dev/agents/shahtuyakov/claude-setup/devops"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/devops/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/shahtuyakov/claude-setup/devops"><img src="https://agentmods.dev/badge/agents/shahtuyakov/claude-setup/devops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00068 | $0.01603 |
| Opus 5.5 | $0.00027 | $0.00641 |
| Sonnet 5.5 | $0.00014 | $0.00321 |
| Haiku 4.5 | $0.00007 | $0.00160 |
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 1mo 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.
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)
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.
- 1mo ago First seen · 237 lines · 68 tokens per session scan A e568e6a870ed
devops is an agent published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 9mo ago), licensed MIT. It adds 68 tokens to every session and 1,603 once invoked, about $0.0003 per session on Opus 5.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.
Other agents, from other repositories
devops-engineer
Use for CI/CD, infrastructure-as-code, containerization, and deployment strategy — authoring or fixing pipelines, Dockerfiles, Terraform/Helm/k8s manifests, and choosing a safe rollout (blue-green, canary) with a rollback path. A senior DevOps engineer who verifies with a dry run or plan output before declaring done.…
devops-engineer
A DevOps engineering role for building and reviewing software delivery systems, infrastructure, and monitoring. DevOps combines development and operations so software can be built, deployed, and maintained reliably.
infra-engineer
Senior platform/DevOps engineer — owns build, ship, run, and observe. Covers Docker/compose, CI/CD (GitHub Actions), deploy targets (Vercel/Render/Fly/AWS), env + config management + 12-factor, observability (structured logs, metrics, tracing, error tracking), health checks, scaling + cost, IaC, rollback/ blue-green…
devops-engineer
CI/CD, containers, IaC, deploys and monitoring, each with a preview and rollback plan. Use to set up or fix CI, write Dockerfiles or Terraform, or plan a deploy.
soleur-engineering-infra-platform-strategist
Use this agent when you need to make infrastructure and deployment strategy decisions before implementation. Evaluates build pipelines, CI/CD approaches, cloud resource selection, containerization strategies, and deployment topology. Use soleur-engineering-infra-terraform-architect for generating Terraform configs…
devops-engineer
Use this agent when the project's external runtime dependencies — database, cache, queue, SMTP, object storage, third-party APIs — must run locally in containers, and for CI/CD work once the local-proof gate has passed. Owns docker-compose, dev Dockerfiles, .env.example, seed/reset scripts, service emulators, and CI…