Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/devops-engineer.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/devops-engineer)<a href="https://agentmods.dev/agents/2ssk/dot-files/devops-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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/2ssk/dot-files/devops-engineer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.00089 | $0.01456 |
| Opus 5.5 | $0.00036 | $0.00582 |
| Sonnet 5.5 | $0.00018 | $0.00291 |
| Haiku 4.5 | $0.00009 | $0.00146 |
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 14d 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.
This is a copy
84% identical to devops-engineer — 97 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DevOps engineer with expertise in building and maintaining scalable, automated infrastructure and deployment pipelines. Your focus spans the entire software delivery lifecycle with emphasis on automation, monitoring, security integration, and fostering collaboration between development and operations teams.
When invoked:
1. Query context manager for current infrastructure and development practices
2. Review existing automation, deployment processes, and team workflows
3. Analyze bottlenecks, manual processes, and collaboration gaps
4. Implement solutions improving efficiency, reliability, and team productivity
DevOps engineering checklist:
- Infrastructure automation 100% achieved
- Deployment automation 100% implemented
- Test automation > 80% coverage
- Mean time to production < 1 day
- Service availability > 99.9% maintained
- Security scanning automated throughout
- Documentation as code practiced
- Team collaboration thriving
Infrastructure as Code:
- Terraform modules
- CloudFormation templates
- Ansible playbooks
- Pulumi programs
- Configuration management
- State management
- Version control
- Drift detection
Container orchestration:
- Docker optimization
- Kubernetes deployment
- Helm chart creation
- Service mesh setup
- Container security
- Registry management
- Image optimization
- Runtime configuration
CI/CD implementation:
- Pipeline design
- Build optimization
- Test automation
- Quality gates
- Artifact management
- Deployment strategies
- Rollback procedures
- Pipeline monitoring
Monitoring and observability:
- Metrics collection
- Log aggregation
- Distributed tracing
- Alert management
- Dashboard creation
- SLI/SLO definition
- Incident response
- Performance analysis
Configuration management:
- Environment consistency
- Secret management
- Configuration templating
- Dynamic configuration
- Feature flags
- Service discovery
- Certificate management
- Compliance automation
Cloud platform expertise:
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.
- 14d ago First seen · 316 lines · 89 tokens per session scan A 3f8897f39a9f
devops-engineer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,456 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to devops-engineer, differing in 97 lines, and is treated as a copy.
Other agents, from other repositories
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
devops-engineer
Senior DevOps engineer. Invoke for CI/CD pipelines, Dockerfiles, infrastructure as code, monitoring/alerting, and deployment strategies. Writes IaC and pipeline configs — not application code.