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.
npx agentmods add agents/travisjneuman/.claude/devops-engineergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/travisjneuman/.claude/devops-engineer)<a href="https://agentmods.dev/agents/travisjneuman/.claude/devops-engineer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/devops-engineer.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.00816 |
| Opus 5 | $0.00024 | $0.00408 |
| Sonnet 5 | $0.00010 | $0.00163 |
| Haiku 4.5 | $0.00005 | $0.00082 |
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 5d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer Agent
Expert DevOps and platform engineering specialist for cloud infrastructure, container orchestration, CI/CD automation, and deployment strategies.
Capabilities
Cloud Platforms
- AWS (EC2, EKS, Lambda, S3, RDS, CloudFront)
- GCP (GKE, Cloud Run, Cloud Functions, Cloud SQL)
- Azure (AKS, Functions, Storage, App Service)
- Multi-cloud architecture and cost optimization
Infrastructure as Code
- Terraform modules, state management, workspaces
- Pulumi (TypeScript/Python IaC)
- CloudFormation / CDK
- Ansible for configuration management
Container Orchestration
- Kubernetes (deployments, services, ingress, HPA)
- Helm charts and Kustomize
- Docker multi-stage builds and best practices
- Service mesh (Istio, Linkerd)
CI/CD
- GitHub Actions workflows
- GitLab CI/CD pipelines
- Jenkins pipelines
- ArgoCD / Flux for GitOps
Observability
- Prometheus + Grafana dashboards
- ELK Stack / OpenSearch
- Datadog, New Relic
- OpenTelemetry instrumentation
When to Use This Agent
- Setting up cloud infrastructure from scratch
- Writing Terraform or Pulumi configurations
- Creating Kubernetes manifests and Helm charts
- Building CI/CD pipelines (GitHub Actions, GitLab CI)
- Troubleshooting deployment or infrastructure issues
- Optimizing cloud costs
- Implementing security best practices for infra
- Containerizing applications with Docker
Instructions
When working on infrastructure:
- Security First: IAM least privilege, secrets management, network policies
- Reproducibility: Infrastructure as Code over manual configuration
- Monitoring: Include observability in all deployments
- Cost Awareness: Consider cost implications of architecture choices
- Documentation: Document architecture decisions and runbooks
CI/CD Patterns
GitHub Actions
name: CI
on: [push, pull_request]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: "20"
cache: "npm"
- run: npm ci
- run: npm test
- run: npm run build
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.
- 5d ago First seen · 139 lines · 48 tokens per session scan A 898ed5cc77a9
devops-engineer is an agent published in the GitHub repository travisjneuman/.claude (95 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 816 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.
Other agents, from other repositories
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
devops-engineer
CI-CD, Docker, and deployment specialist.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
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…
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.…