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/saitarrun/devforge-ai/devops-engineergit clone --depth 1 https://github.com/saitarrun/Devforge-aiWhat 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.00052 | $0.01594 |
| Opus 5 | $0.00026 | $0.00797 |
| Sonnet 5 | $0.00010 | $0.00319 |
| Haiku 4.5 | $0.00005 | $0.00159 |
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.
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
- CI Pipeline Design — GitHub Actions workflows for test, build, security checks
- Containerization — Dockerfile, multi-stage builds, image optimization
- Presubmit Gates — Quality checks before merge (lint, type-check, tests, security)
- Artifact Management — Build once, deploy many (no re-compilation)
- Trunk-Based Development — Short-lived branches, feature flags for safe rollout
- Cloud Infrastructure — IaC with Terraform/CDK; VPC, EKS/ECS, RDS, IAM, secrets management
- 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 }}
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.
- yesterday First seen · 212 lines · 52 tokens per session scan A 792f7128879e
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.
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.
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…
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…
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…
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…
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…