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/nxtg-ai/forge-plugin/devopsgit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat 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.00000 | $0.01834 |
| Opus 5 | $0.00000 | $0.00917 |
| Sonnet 5 | $0.00000 | $0.00367 |
| Haiku 4.5 | $0.00000 | $0.00183 |
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 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps
Automates infrastructure as code -- Docker multi-stage builds, GitHub Actions pipelines, environment management, and monitoring setup that makes deployments reproducible and reversible.
| Level | L1 Vibe Coder |
| Category | Domain Specialist |
| Model | Sonnet |
What It Does
The DevOps agent handles everything between "it works on my machine" and "it works in production." It creates Docker configurations with multi-stage builds for minimal images, GitHub Actions workflows for automated testing and deployment, environment variable management with template files and secret handling, and monitoring setups with health endpoints and structured logging.
What makes this agent valuable is the operational knowledge it encodes. It knows that Docker images should use multi-stage builds (build stage with dev dependencies, runtime stage with only production artifacts). It knows GitHub Actions should cache npm dependencies and run lint, typecheck, and tests as separate steps for clear failure signals. It knows environment variables belong in .env.example (committed template) and .env (gitignored actual values), never hardcoded in source. These are the practices that experienced DevOps engineers enforce through PRs -- the DevOps agent makes them automatic.
The agent understands the NXTG-Forge infrastructure specifically: WSL2 development environment, Vite dev server on port 5050, Express API on port 5051, npm as the package manager, and GitHub Actions for CI/CD. It creates configurations that work in this specific environment, not generic templates that need extensive modification.
When to Use It
- Setting up CI/CD: When you need GitHub Actions workflows for automated testing, linting, type checking, and deployment on push or PR.
- Containerizing the application: When you need a Docker setup with multi-stage builds, proper base images, security considerations, and docker-compose for development.
- Managing environments: When you need to organize environment variables, create template files, separate development from production config, and handle secrets safely.
- Setting up monitoring: When you need health endpoints, structured logging, error tracking integration (Sentry), and uptime monitoring.
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 · 135 lines · 0 tokens per session scan A c29c91d33249
devops is an agent published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,834 tokens. 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
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.
pact-devops-engineer
Use this agent to implement infrastructure and build systems: CI/CD pipelines, Dockerfiles, shell scripts, Makefiles, and infrastructure as code. Use after architectural specifications are ready.
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.