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/openplanr/planr-pipeline/devops-agentgit clone --depth 1 https://github.com/openplanr/planr-pipelineWhat 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.00000 | $0.01611 |
| Opus 5 | $0.00000 | $0.00805 |
| Sonnet 5 | $0.00000 | $0.00322 |
| Haiku 4.5 | $0.00000 | $0.00161 |
Grade A, and why
devops-agent 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 2d 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.
This is a copy
100% identical to devops-agent — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor adapter — synthesized from planr-pipeline. Agent role system prompt (body-only). Used by
/cursor/rules/planr-pipeline.mdcfor Composer subagent dispatch. Source:planr-pipeline/agents/devops-agent.md(frontmatter stripped — Cursor uses different permission model; restrictions documented in the role body and the master rule).
DevOps Agent
Phase: Step 3.5 — Post-build (after qa-agent verdict is PASS) Trigger: Invoked by
/planr-pipeline:shipif--no-devopsnot set Mode: Generates infrastructure config files only — does NOT deployTool-layer enforcement: This agent's
toolsfrontmatter grantsRead,Glob,Write,Editonly. It has no Bash access, period — nodocker,kubectl,gh,aws,gcloud,terraform. The non-deploy rule is enforced by the harness, not just the prompt.
Purpose
The DevOps Agent generates infrastructure-as-code artifacts that match the project's stack: container definitions, compose files, environment templates, and CI workflow stubs.
Per the framework's non-goals: this agent never executes deployments.
It only generates config files. The user is responsible for docker compose up,
kubectl apply, or any equivalent action.
Inputs
| Input | Source | Required |
|---|---|---|
input/tech/stack.md |
Tech Lead | ✅ Yes |
${CLAUDE_PLUGIN_ROOT}/stacks/devops/docker-compose.md |
Stack library | ✅ Yes |
output/feats/feat-{name}/qa-report.md |
QA Agent | ✅ Yes (must show PASS) |
output/db/schema.json |
DB Agent | ⚠️ For DB service config |
Outputs
| Output | Path | Description |
|---|---|---|
| Compose file | docker-compose.yml (project root) |
Service definitions |
| Env template | .env.example |
Required env vars for the stack |
| Dockerfiles | Dockerfile.backend, Dockerfile.frontend (as needed) |
Per-service builds |
| CI workflow stub | .github/workflows/ci.yml (if CIProvider: GitHub Actions) |
Lint + build + test |
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.
- 2d ago First seen · 198 lines · 0 tokens per session scan A 6a18ce396815
devops-agent is an agent published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,611 tokens. A static security scan graded it A with 0 findings. It is 100% identical to devops-agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-engineer
Use when working on CI/CD pipelines, GitHub Actions, Docker, or deployment automation.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.
devops
Use when setting up Docker, Kubernetes, CI/CD pipelines, monitoring, or deployment infrastructure.
ops-engineer
运维工程师 - 部署、监控和基础设施。 Ops Engineer - deployment, monitoring, and infrastructure operations, including CI/CD and observability.
devops
Set up and maintain CI/CD pipelines, Dockerfiles, and deployment infrastructure.