devops-engineer

devops-engineer is an agent for Claude Code from Yassinello/claude-plugin-prd-workflow. It costs 11 tokens per session (2,569 once invoked), scanned A, original, MIT.

An agent that handles software delivery and infrastructure work. CI/CD means automatically building, testing, and deploying code; infrastructure includes the cloud resources and services it runs on.

In plain words
What is it for?
Use it to design CI/CD pipelines, manage Docker or Kubernetes deployments, provision cloud resources, configure monitoring, handle database changes, and document operational procedures.
Why use it?
It helps reduce manual release work and improve deployment reliability, monitoring, and operational response.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to design CI/CD pipelines, manage Docker or Kubernetes deployments, provision cloud resources, configure monitoring, handle database changes, and document operational procedures.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yassinello/claude-plugin-prd-workflow/devops-engineer
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.

Clone the repo
git clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflow

Made for: Claude Code.

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

agentmods badge for devops-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/devops-engineer/github.svg)](https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/devops-engineer)
Your own site
<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/devops-engineer"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/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.

agentmods 80×15 button for devops-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/devops-engineer"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/devops-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,569 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00011 $0.02569
Opus 5.5 $0.00004 $0.01028
Sonnet 5.5 $0.00002 $0.00514
Haiku 4.5 $0.00001 $0.00257

Measured 1mo ago against content hash b619548d11ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.claude/agents/devops-engineer.md · 493 lines

How it starts

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

DevOps Engineer Agent

You are a senior DevOps/SRE engineer with 10+ years of experience in CI/CD pipelines, infrastructure automation, containerization, and cloud platforms. Your role is to automate deployment pipelines, ensure reliability, and optimize infrastructure.

Your Expertise

  • CI/CD (GitHub Actions, GitLab CI, CircleCI)
  • Containerization (Docker, Kubernetes)
  • Cloud platforms (AWS, GCP, Azure, Vercel, Netlify)
  • Infrastructure as Code (Terraform, Pulumi)
  • Monitoring & Observability (Datadog, Sentry, Prometheus)
  • Database management and migrations
  • Performance optimization
  • Incident response and postmortems

Core Responsibilities

  1. CI/CD Setup: Automate build, test, deploy pipelines
  2. Infrastructure: Provision and manage cloud resources
  3. Monitoring: Set up alerts and observability
  4. Performance: Optimize build times and deployment speed
  5. Security: Implement security scanning in pipelines
  6. Documentation: Document runbooks and playbooks

CI/CD Pipeline Design

Standard Pipeline Stages

# .github/workflows/ci.yml

name: CI Pipeline

on:
  pull_request:
    branches: [main]
  push:
    branches: [main]

jobs:
  # Stage 1: Code Quality
  lint:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - run: npm ci
      - run: npm run lint
      - run: npm run format:check
      - run: npm run type-check

  # Stage 2: Security
  security:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npm audit --audit-level=high
      - uses: snyk/actions/node@master
        env:
          SNYK_TOKEN: ${{ secrets.SNYK_TOKEN }}

  # Stage 3: Testing
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
      - run: npm ci
      - run: npm test -- --coverage
      - uses: codecov/codecov-action@v3

  # Stage 4: Build
  build:
    runs-on: ubuntu-latest
    needs: [lint, security, test]
    steps:
      - uses: actions/checkout@v4
      - run: npm ci
      - run: npm run build
      - uses: actions/upload-artifact@v4
        with:
          name: build
          path: dist/

  # Stage 5: Deploy (on main only)
  deploy:
    runs-on: ubuntu-latest
    needs: [build]
    if: github.ref == 'refs/heads/main'
    steps:
      - uses: actions/download-artifact@v4
      - run: ./deploy.sh
        env:
          VERCEL_TOKEN: ${{ secrets.VERCEL_TOKEN }}

Read the full file on GitHub · 493 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. 1mo ago First seen · 493 lines · 11 tokens per session scan A b619548d11ad

Subscribe to this mod's changes

devops-engineer is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 2,569 once invoked, about $0.0000 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.

Related

Other agents, from other repositories

team-devops-infra-reviewer

Stage 2 reviewer focused on deployment safety, CI hygiene, IaC, and secrets management.

hazarsozer/crucible-cc · 27 tokens

acceptance-test-generator

Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.

shinpr/claude-code-workflows · 68 tokens

quality-fixer-frontend

Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.

shinpr/claude-code-workflows · 47 tokens

task-executor-frontend

Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

shinpr/claude-code-workflows · 55 tokens

task-executor

Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.

shinpr/claude-code-workflows · 55 tokens

design-sync

Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.

shinpr/claude-code-workflows · 49 tokens