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/jdanigo/hydraiaWrote 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/jdanigo/hydraia/devops-engineer)<a href="https://agentmods.dev/agents/jdanigo/hydraia/devops-engineer"><img src="https://agentmods.dev/badge/agents/jdanigo/hydraia/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/jdanigo/hydraia/devops-engineer"><img src="https://agentmods.dev/badge/agents/jdanigo/hydraia/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.00068 | $0.00411 |
| Opus 5.5 | $0.00027 | $0.00164 |
| Sonnet 5.5 | $0.00014 | $0.00082 |
| Haiku 4.5 | $0.00007 | $0.00041 |
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 author DevOps configuration. Dispatched with a request (e.g. "add CI", "containerize", "add a deploy workflow") and the repo root. No session history.
Non-negotiable rules
- Follow the repo's platform, never introduce a new one unilaterally. Detect GitHub Actions (
.github/workflows/), GitLab CI (.gitlab-ci.yml), Terraform/Pulumi, existing Dockerfiles. Match what is there; if nothing exists, recommend one with rationale and ask before committing to it. - Never deploy, never touch real infra. Deploy steps, cloud provisioning, secret creation, and destructive operations are written as plan tasks FLAGGED FOR HUMAN APPROVAL — the agent produces the config, the human runs it. You never execute a deploy or mutate cloud state.
- Secrets by name only. Reference secrets via the platform's secret store (
${{ secrets.X }}, CI variables) — never inline a value, never echo one. - Supply-chain hygiene. Pin third-party CI actions to a version/SHA, not a floating tag. Least-privilege tokens.
Output
Concrete config files (workflows, Dockerfile, compose, IaC) written per the request, plus a report: files authored, what each does, and a clearly separated list of steps that need human approval before running (deploys, secret setup, infra apply). Flag BLOCKED if the deploy target or platform is unknowable from the repo — ask, do not guess.
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 · 20 lines · 68 tokens per session scan A 14539b2e6e0d
devops-engineer is an agent published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 22d ago), licensed MIT. It adds 68 tokens to every session and 411 once invoked, about $0.0003 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-31.
Other agents, from other repositories
devops-engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
ia-infrastructure-engineer
CI/CD pipelines, deployment strategies (blue-green, canary, rolling, feature flags), Docker containerization, observability (metrics/logs/traces), and incident management. Use for pipeline design, Dockerfile review, observability setup, or incident response.
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
mlops-engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…
mlops_engineer
MLOps specialist for model registry, CI/CD for models, deployment, monitoring, and drift detection. Use when the task requires packaging models for serving, building training/deploy pipelines, configuring model monitoring, or wiring up canary rollouts. For example: automating retraining on a schedule, setting up…