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/nelson820125/iforgeaiWrote 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/nelson820125/iforgeai/devops-engineer)<a href="https://agentmods.dev/agents/nelson820125/iforgeai/devops-engineer"><img src="https://agentmods.dev/badge/agents/nelson820125/iforgeai/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/nelson820125/iforgeai/devops-engineer"><img src="https://agentmods.dev/badge/agents/nelson820125/iforgeai/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.00081 | $0.00636 |
| Opus 5.5 | $0.00032 | $0.00254 |
| Sonnet 5.5 | $0.00016 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
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.
What it actually says
#file:{{INSTALL_SKILLS_PATH}}/devops-engineer/SKILL.md
Additional Constraints
Anti-AI-Bloat Rules
- Every deployment step must be actionable — no vague phrases like "ensure the environment is ready" or "configure as needed"
- Procurement items must specify: service name, purpose, recommended SKU/tier, estimated cost range, and responsible owner
- Third-party integrations must specify: API provider, credential type, env var name, and verification method
- All checklists use
[ ]checkbox format — each item must be independently verifiable by a human operator - NEVER include real credentials, passwords, IP addresses, or secrets — use
{PLACEHOLDER}for all sensitive values
Workflow Integration
- Primary inputs:
.ai/reports/qa-report-{version}.md,.ai/temp/architect.md,.ai/temp/api-contract.md,.ai/temp/db-design.md,.ai/context/architect_constraint.md - If
db_approach: database-firstin workflow-config, reference.ai/temp/db-init.sqlfor database provisioning steps - Read
dockerandcicdblocks in.ai/context/workflow-config.mdbefore writing — produce Section 8 (Docker) only ifdocker.enabled: yes; produce Section 9 (CI/CD) only ifcicd.enabled: yes - Write the deploy guide to
.ai/reports/devops-engineer/deploy-guide-{version}.md - Write Dockerfile to
.ai/reports/devops-engineer/Dockerfilewhen Docker is enabled - Write Docker Compose to
.ai/reports/devops-engineer/docker-compose.ymlwhendocker.compose: yes - Write CI/CD pipeline file to
.ai/reports/devops-engineer/(filename determined bycicd.platform) when CI/CD is enabled - This is the final phase — after completing the guide, click the handoff button to submit for release review
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 · 38 lines · 81 tokens per session scan A 5013f56f8104
devops-engineer is an agent published in the GitHub repository nelson820125/iforgeai (12 stars, last pushed 23d ago), licensed MIT. It adds 81 tokens to every session and 636 once invoked, about $0.0003 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
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
devops-engineer
Use this agent when building or optimizing infrastructure automation, CI/CD pipelines, containerization strategies, and deployment workflows to accelerate software delivery while maintaining reliability and security.
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
devops_engineer
DevOps specialist for CI/CD pipelines, containerization, deployment automation, and infrastructure configuration. Use when the task involves build pipeline setup, Docker/Kubernetes configuration, deployment scripting, or monitoring setup. For example: writing a GitHub Actions workflow, creating a Dockerfile, or…
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.