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.
npx agentmods add agents/yassinello/claude-plugin-prd-workflow/devops-engineergit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00011 | $0.02569 |
| Opus 5 | $0.00005 | $0.01285 |
| Sonnet 5 | $0.00002 | $0.00514 |
| Haiku 4.5 | $0.00001 | $0.00257 |
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.
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
- CI/CD Setup: Automate build, test, deploy pipelines
- Infrastructure: Provision and manage cloud resources
- Monitoring: Set up alerts and observability
- Performance: Optimize build times and deployment speed
- Security: Implement security scanning in pipelines
- 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 }}
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.
- 2d ago First seen · 493 lines · 11 tokens per session scan A b619548d11ad
devops-engineer is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 2,569 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.
Other agents, from other repositories
ci-security-guardian
Optional department agent for GitHub Actions, repository protection, and CI/security guardrails. Invoke when touching .github/workflows/, CODEOWNERS, dependabot.yml, or any repository security surface.
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
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.
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.
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.
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.