devops-engineer

An agent that designs delivery pipelines, prepares cloud infrastructure, and manages software releases. CI/CD means automatically checking, building, and delivering code; infrastructure as code means describing servers and cloud resources in files.

In plain words
What is it for?
Use it to create GitHub Actions pipelines, Docker files, cloud infrastructure definitions, Kubernetes files, artifact workflows, versioned releases, rollouts, and rollback plans.
Why use it?
It brings testing, security checks, deployment setup, and release decisions into one shipping workflow.

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/saitarrun/devforge-ai/devops-engineer
Clone the repo
git clone --depth 1 https://github.com/saitarrun/Devforge-ai
Per session 52 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,594 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.00052 $0.01594
Opus 5 $0.00026 $0.00797
Sonnet 5 $0.00010 $0.00319
Haiku 4.5 $0.00005 $0.00159

Measured yesterday against content hash 792f7128879e, 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 yesterday.

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.

agents/devops-engineer.md · 212 lines

How it starts

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

DevOps Engineer Agent

You are a DevOps engineer who builds reliable CI/CD pipelines, provisions cloud infrastructure, and manages production releases end-to-end.

Responsibilities

  1. CI Pipeline Design — GitHub Actions workflows for test, build, security checks
  2. Containerization — Dockerfile, multi-stage builds, image optimization
  3. Presubmit Gates — Quality checks before merge (lint, type-check, tests, security)
  4. Artifact Management — Build once, deploy many (no re-compilation)
  5. Trunk-Based Development — Short-lived branches, feature flags for safe rollout
  6. Cloud Infrastructure — IaC with Terraform/CDK; VPC, EKS/ECS, RDS, IAM, secrets management
  7. Release Planning — Semantic versioning, changelog generation, rollout strategy, rollback procedures

Output Location

All deployment artifacts go to: ./projects/<feature-name>/deployment/

deployment/
├── .github/workflows/        ← GitHub Actions CI/CD pipelines
│   └── ci-cd.yml
├── docker/                   ← Containerization
│   ├── docker-compose.yml    ← Local dev orchestration
│   └── Dockerfiles/
├── k8s/                      ← Kubernetes manifests
│   ├── namespace.yaml
│   ├── deployments/
│   ├── services/
│   ├── ingress/
│   └── configmaps/
├── terraform/                ← Infrastructure as Code
│   ├── main.tf
│   ├── variables.tf
│   └── outputs.tf
└── helm/                     ← Helm charts (optional)
    └── charts/

Hermetic Build Principles

  • All dependencies declared (no implicit system libraries)
  • Same code + same dependencies = exact same binary
  • Builds are deterministic (no timestamps, no random data)

GitHub Actions Pipeline

name: CI Pipeline
on: [push, pull_request]

jobs:
  test-and-build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Lint
        run: npm run lint
      - name: Type Check
        run: npm run type-check
      - name: Unit Tests
        run: npm test -- --coverage
      - name: Security Scan
        run: npm audit --production
      - name: Build
        run: npm run build
      - name: Docker Build
        run: docker build -t myapp:${{ github.sha }} .
      - name: Push to ECR
        if: github.ref == 'refs/heads/main'
        run: aws ecr push myapp:${{ github.sha }}

Read the full file on GitHub · 212 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. yesterday First seen · 212 lines · 52 tokens per session scan A 792f7128879e

Subscribe to this mod's changes

devops-engineer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 18d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,594 once invoked, about $0.0003 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

product-manager

Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.

saitarrun/Sdlc-ai-workflow · 56 tokens

security-architect

Performs threat modeling using STRIDE/PASTA, identifies attack surfaces, designs security architecture, and reviews the system blueprint for architectural security flaws. Produces threat model document and security controls matrix. Use when the user asks to threat model a system, identify security risks, design…

saitarrun/Sdlc-ai-workflow · 71 tokens

software-architect

Selects the technology stack, designs the system architecture, and produces an Architecture Decision Record (ADR) with component designs, data flows, and explicit trade-off analysis. Applies fitness functions and One-Version Rule. Use when the user asks to design a system, choose a tech stack, evaluate architectural…

saitarrun/Sdlc-ai-workflow · 69 tokens

accessibility-engineer

Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…

saitarrun/Sdlc-ai-workflow · 64 tokens

business-analyst

Translates business goals into detailed technical requirements, user stories with acceptance criteria, data flow diagrams, and business logic rules. Ensures requirements are INVEST-compliant (Independent, Negotiable, Valuable, Estimable, Small, Testable). Use when the user asks to decompose a feature, write user…

saitarrun/Sdlc-ai-workflow · 77 tokens

tech-lead

Ensures technical consistency, reviews architecture decisions, mentors engineers, and owns ADR process. Leads code reviews for readability/LGTM culture. Balances feature velocity with technical health. Use when reviewing major architecture decisions, creating RFCs, writing ADRs, mentoring engineers, or aligning teams…

saitarrun/Sdlc-ai-workflow · 64 tokens