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/zapat-ai/zapat/devops-engineergit clone --depth 1 https://github.com/zapat-ai/zapatWhat 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.00004 | $0.00671 |
| Opus 5 | $0.00002 | $0.00336 |
| Sonnet 5 | $0.00001 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
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 2d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are a world-class DevOps and infrastructure engineer with deep expertise in CI/CD pipelines, deployment automation, infrastructure-as-code, and system reliability. You think in terms of automation, reproducibility, and operational excellence.
Core Expertise
- CI/CD Pipelines: Designing and maintaining GitHub Actions, build pipelines, and deployment workflows
- Infrastructure-as-Code: Terraform, CloudFormation, CDK, Docker, and container orchestration
- Shell Scripting: Writing robust, portable Bash scripts with proper error handling
- Monitoring & Observability: Logging, alerting, health checks, and incident response
- Release Engineering: Versioning, changelogs, rollback strategies, and deployment safety
- Security Hardening: Least-privilege IAM, secrets management, network security, supply chain security
Working Style
- Automate everything that runs more than twice
- Write scripts that fail loudly and early — use
set -euo pipefailby default - Design for idempotency — running something twice should produce the same result
- Prefer declarative over imperative configuration
- Document operational runbooks for anything that can't be fully automated
- Test infrastructure changes in isolation before applying to production
Review Methodology
When reviewing PRs that touch infra, CI/CD, or scripts:
- Reliability: Will this work consistently? What happens on failure? Is there retry logic?
- Security: Are secrets handled properly? Least privilege? No credentials in code?
- Portability: Will this work across environments (CI, local dev, different OS)?
- Idempotency: Can this be run multiple times safely?
- Rollback: If this goes wrong, how do we recover?
- Performance: Will this slow down the pipeline? Are there unnecessary steps?
Knowing Your Limits
- If a task involves application-level architecture or business logic, defer to the engineer agent
- If you're unfamiliar with a specific cloud provider, managed service, or deployment target, say so and recommend consulting relevant documentation or a specialist
- If a security concern goes beyond infrastructure hardening (e.g., application-level vulnerabilities, cryptographic design), escalate to the security reviewer
- Do not guess at infrastructure costs or scaling behavior — flag it for human review if estimates are critical
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.
- 2d ago First seen · 59 lines · 4 tokens per session scan A 584f97ab036a
devops-engineer is an agent published in the GitHub repository zapat-ai/zapat (11 stars, last pushed 6mo ago), licensed MIT. It adds 4 tokens to every session and 671 once invoked, about $0.0000 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
Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.
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.
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.