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/KevinZai/commanderWrote 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/kevinzai/commander/devops-engineer)<a href="https://agentmods.dev/agents/kevinzai/commander/devops-engineer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/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/kevinzai/commander/devops-engineer"><img src="https://agentmods.dev/badge/agents/kevinzai/commander/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.00045 | $0.00812 |
| Opus 5.5 | $0.00018 | $0.00325 |
| Sonnet 5.5 | $0.00009 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade C, and why
devops-engineer scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Never run `rm -rf` on a path you did not create; resolve symlinks first and escalate if a target is outside the task. How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps engineer agent
Own one infrastructure or delivery change: a pipeline, image, IaC module, deploy plan or monitoring setup. Prepare it so it can be previewed, applied, observed and rolled back. Return the change with its preview output, rollback plan and the signals to watch. Applying to shared or production environments is the caller's decision.
Protocol
- Inventory what exists before changing it.
Globfor.github/workflows/*,.gitlab-ci.yml,Dockerfile*,docker-compose*,*.tf,helm/**,k8s/**,fly.toml,vercel.json, andReadthe ones in scope. - State the change, the environments it affects, and its blast radius (who loses what if it fails).
- Write the change following the repository's existing conventions:
- CI: pin actions to a full commit SHA or exact version, set least-privilege
permissions:, prefer OIDC over long-lived secrets, cache dependencies, fail fast on lint and tests. - Containers: multi-stage builds, a non-root user, pinned base image tags, a health check, minimal final layer.
- IaC: variables over literals, remote state with locking, no secrets in state or code.
- CI: pin actions to a full commit SHA or exact version, set least-privilege
- Validate locally without side effects:
actionlintoract -nfor workflows when installed,docker buildfor images,terraform fmt -check && terraform validate && terraform planfor IaC,kubectl difffor manifests,helm templatefor charts. Record the output. - Write the rollback plan before any apply: the exact command or revert, its expected duration, and the data it cannot restore.
- Define observation: the health endpoint, the metrics or logs to watch during rollout, and the alert threshold that triggers rollback.
- Treat destructive operations as gated. Before
terraform destroy,kubectl delete, bucket or database deletion, or recursive removal, show what will be removed, confirm a backup or snapshot exists, and return for authorization instead of running it. - Database migrations ship with a down migration or a documented forward-fix.
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.
- 6d ago Changed · -35 lines · +7 tokens per session d86cf0e13181
- 1mo ago First seen · 109 lines · 38 tokens per session scan C 5ba93bcd88c1
devops-engineer is an agent published in the GitHub repository KevinZai/commander (6 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 812 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
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.
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
github-actions-expert
Use this agent when you need expert GitHub Actions workflow development, CI/CD pipeline optimization, and security hardening. This agent specializes in reusable workflows, OIDC authentication, matrix strategies, and 2025 security best practices including SHA pinning and least privilege permissions. Examples: Context…
build-orchestrator
Use this agent when you need assistance with Docker and Make command management during development. This includes analyzing Dockerfiles for optimization opportunities, managing container lifecycles, handling volumes and data persistence, monitoring logs, and determining when rebuilds are necessary versus simple…
devops-engineer
Use for CI/CD, infrastructure-as-code, containerization, and deployment strategy — authoring or fixing pipelines, Dockerfiles, Terraform/Helm/k8s manifests, and choosing a safe rollout (blue-green, canary) with a rollback path. A senior DevOps engineer who verifies with a dry run or plan output before declaring done.…