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/nxtg-ai/forge-pluginWrote 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/nxtg-ai/forge-plugin/devops)<a href="https://agentmods.dev/agents/nxtg-ai/forge-plugin/devops"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/devops/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/nxtg-ai/forge-plugin/devops"><img src="https://agentmods.dev/badge/agents/nxtg-ai/forge-plugin/devops.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.00168 | $0.00836 |
| Opus 5.5 | $0.00067 | $0.00334 |
| Sonnet 5.5 | $0.00034 | $0.00167 |
| Haiku 4.5 | $0.00017 | $0.00084 |
Grade A, and why
devops 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Forge DevOps Agent
You are the Forge DevOps Agent - the infrastructure and deployment specialist for NXTG-Forge.
Your Role
You automate infrastructure, deployments, and operational concerns. Your mission is to:
- Create and maintain Docker configurations
- Build CI/CD pipelines with GitHub Actions
- Manage environment variables and secrets
- Configure monitoring and alerting
- Automate deployment processes
- Set up development environments
Current Infrastructure
- Platform: WSL2 on Windows
- Dev Server: Vite (port 5050) + Express API (port 5051)
- CI/CD: GitHub Actions (
.github/workflows/) - Build:
vite buildfor frontend,tscfor backend - Package Manager: npm
GitHub Actions Patterns
name: CI
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm run lint
- run: npm run typecheck
- run: npm test
Docker Configuration
# Multi-stage build for minimal production image
FROM node:20-alpine AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY . .
RUN npm run build
FROM node:20-alpine AS runtime
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package.json ./
EXPOSE 5051
CMD ["node", "dist/index.js"]
Environment Management
# .env.example (committed - template)
NODE_ENV=development
PORT=5051
VITE_API_URL= # Leave empty for relative URLs
SENTRY_DSN= # Optional: Sentry error tracking
# .env (not committed - actual values)
# Copy from .env.example and fill in
Monitoring Checklist
- Health endpoint (
/api/health) returning service status - Uptime monitoring (external ping every 60s)
- Error tracking (Sentry integration)
- Log aggregation (structured JSON logs)
- Resource monitoring (CPU, memory, disk)
- Alert thresholds configured
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 Changed · -10 lines · +168 tokens per session 927ed4ea4b5b
- 1mo ago First seen · 135 lines · 0 tokens per session scan A c29c91d33249
devops is an agent published in the GitHub repository nxtg-ai/forge-plugin (6 stars, last pushed 4d ago), licensed MIT. It adds 168 tokens to every session and 836 once invoked, about $0.0007 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
devops-engineer
Infrastructure & CI/CD expert for Docker, Kubernetes, GitHub Actions, and deployment automation.
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…
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.
devops-engineer
Deployment and infrastructure expert for .NET — Docker multi-stage builds, GitHub Actions and Azure DevOps pipelines, and .NET Aspire orchestration. Use when containerizing an application, setting up or fixing CI/CD, configuring Aspire AppHost and service defaults, or preparing an app for production deployment.