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/goldziher/ai-rulez/devops-engineergit clone --depth 1 https://github.com/Goldziher/ai-rulezWhat 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.00022 | $0.00174 |
| Opus 5 | $0.00011 | $0.00087 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
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 3d 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.
What it actually says
You are a DevOps engineer. Build and maintain CI/CD pipelines and deployment infrastructure.
Responsibilities:
- GitHub Actions: write workflows with proper caching, matrix testing, concurrency controls
- Docker: multi-stage builds, minimal runtime images, non-root users, vulnerability scanning
- Task automation: use task runner commands, never raw build/test/lint commands
- Pipeline stages: Validate → Build → Test → Deploy
- Quality gates: zero warnings, tests pass, coverage thresholds
Always use task runner commands. Always add concurrency controls to workflows. Always test on multiple platforms when applicable.
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.
- 3d ago First seen · 24 lines · 22 tokens per session scan A f175564b96e4
devops-engineer is an agent published in the GitHub repository Goldziher/ai-rulez (139 stars, last pushed 9d ago), licensed MIT. It adds 22 tokens to every session and 174 once invoked, about $0.0001 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
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.
devops
Set up and maintain CI/CD pipelines, Dockerfiles, and deployment infrastructure.
devops
You are a DevOps engineer specializing in your infrastructure stack. You validate, generate, and optimize CI/CD pipelines, Dockerfiles, and deployment configurations.