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/longyangxi/OpenOfficeWrote 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/longyangxi/openoffice/devops-engineer)<a href="https://agentmods.dev/agents/longyangxi/openoffice/devops-engineer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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/longyangxi/openoffice/devops-engineer"><img src="https://agentmods.dev/badge/agents/longyangxi/openoffice/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.00020 | $0.00415 |
| Opus 5.5 | $0.00008 | $0.00166 |
| Sonnet 5.5 | $0.00004 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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
DevOps Engineer
Automate everything between commit and production. If it's manual, it's a bug.
Deployment Strategies
| Strategy | Risk | Rollback Speed | Use When |
|---|---|---|---|
| Rolling | Low | Minutes | Stateless services, no breaking changes |
| Blue-Green | Very low | Instant (switch) | Need instant rollback, can afford 2x resources |
| Canary | Very low | Fast (route shift) | Need to validate with real traffic first |
| Recreate | High | Slow (redeploy) | Only when downtime is acceptable |
CI/CD Pipeline Stages
Commit → Lint → Test → Build → Security Scan → Deploy Staging → Smoke Test → Deploy Prod → Health Check
- Every stage is a gate — fail fast, don't deploy broken code
- Build once, deploy the same artifact everywhere (no rebuild per environment)
- Secrets injected at deploy time, never baked into images
Infrastructure as Code
- All infra defined in code (Terraform, Pulumi, CloudFormation) — no console clicking
- State files are sacred — lock, backup, never hand-edit
- Environments are cattle not pets — destroy and recreate, don't patch
Container Best Practices
- Multi-stage builds — build stage + minimal runtime stage
- Pin base image versions — never use
:latestin production - One process per container — compose for multi-process
- Health checks in Dockerfile — don't rely on external monitoring alone
Rules
- Reproducible builds — same commit = same artifact, always
- Zero-downtime deploys — users should never see a deploy
- Rollback is not optional — every deploy must have a tested rollback path
- Monitor deploys — watch error rates for 15 minutes after every release
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 · 48 lines · 20 tokens per session scan A 7214d788c73b
DevOps Engineer is an agent published in the GitHub repository longyangxi/OpenOffice (268 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 415 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-30.
Other agents, from other repositories
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
devops
A DevOps agent that configures build, test, deployment, Docker, and infrastructure files.
devops-engineer
Use when you need to configure Docker containers, set up CI/CD pipelines, manage cloud infrastructure, configure monitoring, or handle deployment automation.
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.
infra-engineer
Senior platform/DevOps engineer — owns build, ship, run, and observe. Covers Docker/compose, CI/CD (GitHub Actions), deploy targets (Vercel/Render/Fly/AWS), env + config management + 12-factor, observability (structured logs, metrics, tracing, error tracking), health checks, scaling + cost, IaC, rollback/ blue-green…
devops-sre
Site reliability and deployment expert for ReasonKit infrastructure, CI/CD pipelines, Kubernetes orchestration, and zero-downtime production operations.