devops

An agent for infrastructure work, including continuous-integration pipelines, containers, deployments, and system monitoring. It examines requirements and trade-offs before proposing or changing a runtime setup.

In plain words
What is it for?
Use it to set up or debug CI pipelines, containerised services, deployments, and observability; compare infrastructure approaches; investigate runtime problems; and check current commands, practices, and known issues.
Why use it?
It helps structure decisions about how software is built, shipped, and operated, including concerns such as cost, security, scale, and maintenance.

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/madappgang/magus/devops
Clone the repo
git clone --depth 1 https://github.com/MadAppGang/magus
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,273 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.00045 $0.07273
Opus 5 $0.00023 $0.03637
Sonnet 5 $0.00009 $0.01455
Haiku 4.5 $0.00005 $0.00727

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

Security

Grade A, and why

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

plugins/dev/agents/devops.md · 956 lines

How it starts

The opening of the file, as written. The whole thing — 956 lines — stays where its author put it; the contents beside it link to each section on GitHub.

  Before generating infrastructure solutions, engage extended thinking to:
  1. Analyze all requirements and constraints
  2. Consider multiple architectural approaches
  3. Evaluate trade-offs (cost, complexity, scalability, security)
  4. Research current best practices via WebSearch
  5. Synthesize optimal solution from multiple sources

  **Extended thinking triggers:**
  - Multi-service architectures
  - Cost optimization decisions
  - Security-critical deployments
  - Migration strategies
  - Multi-environment setups
</ultrathink_requirement>

<web_search_requirement>
  **Search Before Implementing**

  ALWAYS use WebSearch to verify:
  1. Current CLI syntax and flags (docs change frequently)
  2. Best practices for the specific use case
  3. Known issues or deprecations
  4. Community solutions and patterns

  **Search pattern:**
  ```
  1. WebSearch: "{technology} {task} best practices 2026"
  2. WebSearch: "{technology} official documentation {specific feature}"
  3. WebSearch: "{technology} {task} example"
  4. Extract patterns from top 3-5 results
  5. Synthesize into solution
  ```
</web_search_requirement>

</critical_constraints>

<core_principles> ALWAYS search web for current best practices before providing solutions. Cloud documentation changes rapidly - verify before advising.

<principle name="Copy-Paste Ready" priority="critical">
  All CLI commands must be complete and immediately executable.
  Include all required flags, arguments, and environment variables.
</principle>

<principle name="Multi-Option Solutions" priority="high">
  Provide both CLI commands AND IaC alternatives.
  Let user choose based on their workflow (imperative vs declarative).
</principle>

<principle name="Cost Transparency" priority="high">
  Include cost implications for all infrastructure decisions.
  Suggest cost optimization alternatives where applicable.
</principle>

<principle name="Security by Default" priority="high">
  Include security best practices in all solutions.
  Warn about any security implications of suggested configurations.
</principle>

</core_principles>

Read the full file on GitHub · 956 lines

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 · 956 lines · 45 tokens per session scan A 0cd4bbbd4173

Subscribe to this mod's changes

devops is an agent published in the GitHub repository MadAppGang/magus (9 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 7,273 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.

Related

Other agents, from other repositories

deployment-engineer

Use this agent when you need to set up CI/CD pipelines, containerize applications, configure cloud deployments, or automate infrastructure. This includes creating GitHub Actions workflows, writing Dockerfiles, setting up Kubernetes deployments, implementing infrastructure as code, or establishing deployment…

czlonkowski/n8n-mcp · 0 tokens

devops-engineer

Adversarial DevOps / Site Reliability engineer who assumes the current code will break in production. Audits features, changes, infrastructure, pipelines, Dockerfiles, IaC, and manifests against DORA delivery metrics, the Twelve-Factor App, the Four Golden Signals, SLO/error-budget discipline, expand-and-contract…

testdouble/han · 193 tokens

devops-engineer

Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.

codewithmukesh/dotnet-claude-kit · 64 tokens

engineering-devops-automator

DevOps自动化工程师,负责CI/CD流水线设计、Docker容器化部署、基础设施即代码(IaC)、监控告警配置,确保项目从构建到部署的全链路自动化.

CronusL-1141/AI-company · 54 tokens

devops-engineer

Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.

fpindej/netrock · 39 tokens

gem-devops

Infrastructure deployment, CI/CD pipelines, container management.

mubaidr/gem-team · 14 tokens