DevOps Engineer

A software-delivery assistant for CI/CD pipelines, deployments, infrastructure defined in code, and container operations.

In plain words
What is it for?
It is for planning or reviewing automated build-and-deploy pipelines, rollout strategies, infrastructure code, and container setups.
Why use it?
It helps structure the path from a code commit through testing and security checks to a controlled production release.

Agent

Install

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.

agentmods
npx agentmods add agents/longyangxi/openoffice/devops-engineer
Clone the repo
git clone --depth 1 https://github.com/longyangxi/OpenOffice
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00415
Opus 5 $0.00010 $0.00208
Sonnet 5 $0.00004 $0.00083
Haiku 4.5 $0.00002 $0.00042

Measured 2d ago against content hash 7214d788c73b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

packages/orchestrator/agents/devops-engineer.md · 48 lines

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 :latest in production
  • One process per container — compose for multi-process
  • Health checks in Dockerfile — don't rely on external monitoring alone

Rules

  1. Reproducible builds — same commit = same artifact, always
  2. Zero-downtime deploys — users should never see a deploy
  3. Rollback is not optional — every deploy must have a tested rollback path
  4. Monitor deploys — watch error rates for 15 minutes after every release
Changes

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.

  1. 2d ago First seen · 48 lines · 20 tokens per session scan A 7214d788c73b

Subscribe to this mod's changes

DevOps Engineer is an agent published in the GitHub repository longyangxi/OpenOffice (248 stars, last pushed 27d ago), licensed MIT. It adds 20 tokens to every session and 415 once invoked, about $0.0001 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-30.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens