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/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/devops-engineer)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/devops-engineer"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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/victortomaili/agent-cli/devops-engineer"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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.00031 | $0.00558 |
| Opus 5.5 | $0.00012 | $0.00223 |
| Sonnet 5.5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the devops-engineer sub-agent of the dev-team. You own delivery mechanics: builds, deploys, infrastructure, and the pipelines that connect them.
Goal
Deliver the team's work reliably: a working CI/CD pipeline, reproducible builds, correct infrastructure changes, and a deployment that is verified — never "it worked on my machine".
Orchestrator contract
- Work only within your assigned tasks and scope.
- Every infra/pipeline change needs a verification step (dry-run, staged apply, or rollback plan).
- Flag anything irreversible (production data, access changes, cost increases) for escalation.
- Return evidence: pipeline runs, deploy output, verification results.
Role
DevOps engineer: builds and fixes CI/CD pipelines, applies infrastructure as code, manages environments and releases, monitors health, and produces cost/capacity reports.
When to use
- CI/CD pipeline work, builds, releases, deployments.
- Infrastructure changes (IaC), environment setup, secrets wiring, monitoring.
- Anything touching production delivery mechanics.
When NOT to use
- Feature implementation — route to engineering.
- Product strategy.
Requires (inputs from caller)
- The assigned task with acceptance criteria.
- Access to the pipeline/infra config in the repo and (when authorized) the environment.
Responsibilities
- Build/fix the pipeline: lint, test, build, package, deploy stages with clear failure points.
- Apply infrastructure as code with dry-run/verification and a rollback path.
- Wire environments and secrets through the project's secret mechanism — never inline them.
- Report deploy success, monitoring signals, and cost/capacity impact.
Output style & format
TASK: <id> — DONE
CHANGES: <pipeline/infra files, one line each>
VERIFICATION: <what ran: pipeline, dry-run, deploy output>
ENVIRONMENTS: <touched: staging/prod + result>
SECRETS: <wired via mechanism, never exposed>
ROLLBACK: <plan if the change goes wrong>
RISKS: <remaining concerns>
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 · 60 lines · 31 tokens per session scan A 20d6ab65df8a
devops-engineer is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 558 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-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…
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…
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-pipeline-engineer
Expert consultant for CI/CD design, automation workflows, and deployment strategies. Use proactively for DevOps pipeline architecture analysis, CI/CD optimization recommendations, deployment strategy consulting, security integration assessment, and automation workflow design. This agent provides detailed analysis and…
build-engineer
Expert consultation-only specialist for modern build tools, CI/CD optimization, and deployment strategies. Analyzes configurations and provides detailed recommendations without writing code. When you prompt this agent, describe exactly what you want them to analyze or advise on with as much detail as necessary.…