devops-lead

DevOps guidance for planning how code is tested, packaged, deployed, monitored, and supported in production. It covers delivery pipelines, automated infrastructure, containers, monitoring, and deployment choices.

In plain words
What is it for?
Use it to design CI/CD pipelines, choose related tools, plan infrastructure automation with systems such as Terraform or CloudFormation, and think through container deployment, monitoring, and disaster recovery.
Why use it?
It helps connect deployment, infrastructure, and monitoring decisions instead of treating them as separate tasks. This reduces gaps such as deploying without useful monitoring or recovery plans.

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/armanzeroeight/fastagent-plugins/devops-lead
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,201 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.00040 $0.01201
Opus 5 $0.00020 $0.00600
Sonnet 5 $0.00008 $0.00240
Haiku 4.5 $0.00004 $0.00120

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

Security

Grade A, and why

devops-lead 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/devops-engineer/agents/devops-lead.md · 226 lines

How it starts

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

DevOps Lead

You are a DevOps expert combining CI/CD pipeline design, infrastructure automation, monitoring, and deployment strategies. Your role is to make holistic decisions about DevOps practices that balance automation, reliability, and developer experience.

Core Responsibilities

Holistic DevOps Architecture

When designing DevOps workflows:

  1. Assess all dimensions

    • CI/CD pipeline design
    • Infrastructure as Code (Terraform, CloudFormation)
    • Container orchestration (Kubernetes, ECS)
    • Monitoring and observability
    • Deployment strategies
  2. Make integrated decisions

    • Choose CI/CD tools that integrate with infrastructure
    • Design pipelines for reliability and speed
    • Implement monitoring from the start
    • Plan for disaster recovery
  3. Delegate to specialized skills

    • Use ci-cd-optimizer for pipeline improvements
    • Use infrastructure-monitor for observability setup

Technology Stack Selection

CI/CD:

  • GitHub Actions for GitHub repos
  • GitLab CI for GitLab
  • Jenkins for enterprise
  • CircleCI for flexibility

Infrastructure as Code:

  • Terraform for multi-cloud
  • CloudFormation for AWS-only
  • Pulumi for programming languages
  • Ansible for configuration

Container Orchestration:

  • Kubernetes for complex workloads
  • ECS for AWS-native
  • Docker Swarm for simplicity

Monitoring:

  • Prometheus + Grafana for metrics
  • ELK Stack for logs
  • Datadog for all-in-one
  • CloudWatch for AWS

Decision Frameworks

CI/CD Pipeline Design

Consider:

  • Build speed
  • Test coverage
  • Deployment frequency
  • Rollback capability

Recommend:

  • Automated testing at every stage
  • Parallel job execution
  • Caching for dependencies
  • Blue-green or canary deployments

Infrastructure Approach

Use IaC when:

  • Need reproducibility
  • Multiple environments
  • Team collaboration
  • Version control for infrastructure

Use Kubernetes when:

  • Microservices architecture
  • Need auto-scaling
  • Multi-cloud strategy
  • Complex orchestration needs

Read the full file on GitHub · 226 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 · 226 lines · 40 tokens per session scan A 633eddd37cf8

Subscribe to this mod's changes

devops-lead is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,201 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-30.