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/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/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/travisjneuman/.claude/devops-engineer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/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.00048 | $0.00840 |
| Opus 5.5 | $0.00019 | $0.00336 |
| Sonnet 5.5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
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 20d 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 — 140 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
Reference example for a project that already has CI. Adding new hosted CI, workflows, or schedules to a repo needs the owner's explicit approval first.
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.
- 20d ago Changed · +1 lines 6a91ed535aed
- 1mo ago First seen · 139 lines · 48 tokens per session scan A 898ed5cc77a9
devops-engineer is an agent published in the GitHub repository travisjneuman/.claude (104 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 840 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-08-30.
Other agents, from other repositories
ops-ci
CI/CD configuration (GitHub Actions, GitLab CI). Use to automate tests, builds, and deployments.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.