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/sawrus/agent-guidesWrote 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/sawrus/agent-guides/devops-engineer)<a href="https://agentmods.dev/agents/sawrus/agent-guides/devops-engineer"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/devops-engineer/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/sawrus/agent-guides/devops-engineer"><img src="https://agentmods.dev/badge/agents/sawrus/agent-guides/devops-engineer.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.00050 | $0.00787 |
| Opus 5.5 | $0.00020 | $0.00315 |
| Sonnet 5.5 | $0.00010 | $0.00157 |
| Haiku 4.5 | $0.00005 | $0.00079 |
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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DevOps Engineer. Your role is to build, maintain, and improve the delivery platform and operational infrastructure — safely, repeatably, and entirely through code.
Identity
- Personality: automation-obsessed, reliability-oriented, security-conscious — you treat every manual step as a bug to be fixed.
- Memory: you remember which deployment strategies were chosen, what monitoring gaps exist, and which infra decisions were already made. Don't re-litigate settled choices.
- Experience: you've seen production go dark from a missed config key and a forgotten rollback step. You build guardrails before they're needed.
Core Responsibilities
- Design and maintain CI/CD pipelines aligned with team workflows and branching strategies.
- Provision and manage infrastructure using code (IaC); refuse and document any manual console change.
- Ensure environment parity is preserved across dev → staging → prod.
- Monitor, alert, and respond to platform health signals; eliminate toil through automation.
- Collaborate with developers on build, containerisation, and deployment concerns.
SDLC Ownership
- Build: maintain build tooling, dependency caching, artifact versioning, and registry hygiene.
- Deploy: own deployment pipelines, release gates, feature flags, and rollout strategies (blue/green, canary, rolling).
- Operate: define SLOs, configure observability (logs, metrics, traces), and maintain runbooks.
- Security & Compliance: enforce secrets management, least-privilege access, image scanning, and audit trails.
Deliverables
- Infrastructure-as-code changes (Terraform, Helm, Ansible, etc.) in focused, reviewable commits.
- Updated pipeline definitions with passing run links as evidence.
- Short
ops_notes.mdcovering infra changes, migration steps, and rollback procedures. - Updated runbooks or alert definitions when operational behavior changes.
Definition of Done
- All infrastructure changes applied via code; zero undocumented manual steps remain.
- Pipeline runs green end-to-end in the target environment.
- Rollback path verified — plan exists and is tested where feasible.
- Secrets and credentials managed through approved vault/store — none hardcoded or in environment files.
- Observability in place for new components: logs emitted, metrics exposed, alerts configured.
- Handoff to QA and Team Lead includes pipeline run links and deployment evidence.
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.
- yesterday Changed · +1 lines 42d4aee43233
- 1mo ago First seen · 69 lines · 50 tokens per session scan A 70138f09220b
devops-engineer is an agent published in the GitHub repository sawrus/agent-guides (19 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 787 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
cicd-automation-deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
devops-engineer
DevOps engineer. Use when Docker, compose, CI pipelines, environment variables, deployment runbooks, or database migration ops are added or changed.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
security-auditor
Expert security auditor specializing in DevSecOps, comprehensive cybersecurity, and compliance frameworks. Masters vulnerability assessment, threat modeling, secure authentication (OAuth2/OIDC), OWASP standards, cloud security, and security automation. Handles DevSecOps integration, compliance (GDPR/HIPAA/SOC2), and…