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.
git clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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.
[](https://agentmods.dev/agents/saitarrun/devforge-ai/devops-engineer)<a href="https://agentmods.dev/agents/saitarrun/devforge-ai/devops-engineer"><img src="https://agentmods.dev/badge/agents/saitarrun/devforge-ai/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.
<a href="https://agentmods.dev/agents/saitarrun/devforge-ai/devops-engineer"><img src="https://agentmods.dev/badge/agents/saitarrun/devforge-ai/devops-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00052 | $0.01594 |
| Opus 5.5 | $0.00021 | $0.00638 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 212 lines · 52 tokens per session scan A 792f7128879e
devops-engineer is an agent published in the GitHub repository saitarrun/Devforge-ai (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,594 once invoked, about $0.0002 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-31.
Other agents, from other repositories
change
Changelog and release communication — breaking change documentation, deprecation notices, migration guides.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
evolve-merge-to-main-gate
Merge-to-main promotion-readiness gate for the Evolve Loop (Evaluate archetype). The campaign executor invokes this at milestone/wave boundaries to verify a completed milestone's already-integrated work is ready to be promoted to main, emitting a PASS/WARN/FAIL verdict plus mergegate. signals. READ-ONLY — it never…
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
gitops-operator
Use when creating, modifying, or reviewing the desired state of a Kubernetes cluster declared in Git — Flux HelmReleases, Argo Applications, Kustomizations, Helm values, manifests, ConfigMaps, Ingress — or when reasoning about reconciliation and drift between Git and the running cluster.
doc-changelog
Changelog maintenance following Keep a Changelog. Use to document changes between versions.