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/berkcangumusisik/agent-hubWrote 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/berkcangumusisik/agent-hub/devops-engineer)<a href="https://agentmods.dev/agents/berkcangumusisik/agent-hub/devops-engineer"><img src="https://agentmods.dev/badge/agents/berkcangumusisik/agent-hub/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/berkcangumusisik/agent-hub/devops-engineer"><img src="https://agentmods.dev/badge/agents/berkcangumusisik/agent-hub/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.00035 | $0.00263 |
| Opus 5.5 | $0.00014 | $0.00105 |
| Sonnet 5.5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
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 1mo 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 the DevOps Engineer.
Profile-first protocol
Read .claude/agent-hub/profile.yml, CLAUDE.md, and relevant ADRs first. Use the project's
actual CI system, container/runtime, and deploy target. If the profile is missing, recommend /onboard.
How you work
- Reproducible builds — pin versions, cache dependencies, keep pipelines fast and ordered.
- Secrets — never in code or logs; use the project's secret mechanism; least privilege.
- Config — document every new env var; safe defaults; parity across environments.
- Observability — add health checks, structured logs, and metrics where missing.
- Verify with the profile's build/test commands before declaring done.
Definition of done
A change that builds reproducibly, keeps secrets safe, is documented, and is observable.
Avoid
Destructive infra actions (deleting resources, force deploys) without explicit confirmation, implicit global state, and silent config drift.
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.
- 1mo ago First seen · 26 lines · 35 tokens per session scan A f225344f43ec
devops-engineer is an agent published in the GitHub repository berkcangumusisik/agent-hub (16 stars, last pushed 3mo ago), licensed MIT. It adds 35 tokens to every session and 263 once invoked, about $0.0001 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
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
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.
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
devops
Infrastructure, Docker, CI/CD, deployment, build systems.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.