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/victortomaili/agent-cli/devops-engineergit clone --depth 1 https://github.com/VictorTomaili/agent-cliWhat 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.00031 | $0.00558 |
| Opus 5 | $0.00015 | $0.00279 |
| Sonnet 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 yesterday.
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.
- yesterday 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 5d ago), licensed MIT. It adds 31 tokens to every session and 558 once invoked, about $0.0002 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-31.
Other agents, from other repositories
vc-update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-validate-agent
VALIDATE MODE - Convert a written plan into an executable contract. Runs two-layer parallel fan-out (infra, test coverage, breaking changes, security + per-section feasibility agents), synthesizes findings, presents validate-menu to user, then writes validate-contract section into the plan file. Mandatory phase…
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.