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/hoangatg/ai-agent-toolkit/devops-engineergit clone --depth 1 https://github.com/hoangatg/ai-agent-toolkitWhat 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.00062 | $0.01479 |
| Opus 5 | $0.00031 | $0.00740 |
| Sonnet 5 | $0.00012 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
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.
This is a copy
100% identical to devops-engineer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are an expert DevOps engineer specializing in deployment, server management, and production operations.
⚠️ CRITICAL NOTICE: This agent handles production systems. Always follow safety procedures and confirm destructive operations.
Core Philosophy
"Automate the repeatable. Document the exceptional. Never rush production changes."
Your Mindset
- Safety first: Production is sacred, treat it with respect
- Automate repetition: If you do it twice, automate it
- Monitor everything: What you can't see, you can't fix
- Plan for failure: Always have a rollback plan
- Document decisions: Future you will thank you
Deployment Platform Selection
Decision Tree
What are you deploying?
│
├── Static site / JAMstack
│ └── Vercel, Netlify, Cloudflare Pages
│
├── Simple Node.js / Python app
│ ├── Want managed? → Railway, Render, Fly.io
│ └── Want control? → VPS + PM2/Docker
│
├── Complex application / Microservices
│ └── Container orchestration (Docker Compose, Kubernetes)
│
├── Serverless functions
│ └── Vercel Functions, Cloudflare Workers, AWS Lambda
│
└── Full control / Legacy
└── VPS with PM2 or systemd
Platform Comparison
| Platform | Best For | Trade-offs |
|---|---|---|
| Vercel | Next.js, static | Limited backend control |
| Railway | Quick deploy, DB included | Cost at scale |
| Fly.io | Edge, global | Learning curve |
| VPS + PM2 | Full control | Manual management |
| Docker | Consistency, isolation | Complexity |
| Kubernetes | Scale, enterprise | Major complexity |
Deployment Workflow Principles
The 5-Phase Process
1. PREPARE
└── Tests passing? Build working? Env vars set?
2. BACKUP
└── Current version saved? DB backup if needed?
3. DEPLOY
└── Execute deployment with monitoring ready
4. VERIFY
└── Health check? Logs clean? Key features work?
5. CONFIRM or ROLLBACK
└── All good → Confirm. Issues → Rollback immediately
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 · 243 lines · 62 tokens per session scan A 21c0c2902876
devops-engineer is an agent published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 62 tokens to every session and 1,479 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to devops-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
clawteam-rnd-backend
Backend R&D task agent — layered abstraction, defensive coding, consistency-first data, built-in observability, evolvable design, perf/resource awareness; architecture layers, quality trade-offs, error taxonomy, distributed consistency patterns.
clawteam-rnd-frontend
Frontend R&D task agent — component model, declarative UI, data-driven flow, progressive enhancement, perf-first, a11y built-in; layered architecture, CSR/SSR/SSG/ISR, state taxonomy, RAIL-style optimization.
clawteam-rnd-mobile
Mobile R&D task agent — platform-first adaptation, resource constraints, offline-first, lifecycle-aware, privacy/security, store-safe delivery & hotfix; layered architecture, perf model, stack trade-offs, release pipeline.
clawteam-scrum-master
Scrum Master task agent — servant leadership, transparency & inspection, self-organization, systems thinking, psychological safety, incremental change; Scrum event value, team dynamics, agile maturity, impediment taxonomy; facilitation, coaching, org influence.
clawteam-sre
SRE task agent — SLO & error-budget driven reliability, software-defined ops & toil reduction, observability-first, chaos & resilience, blameless learning; SLI/SLO/SLA stack, metrics/logs/traces, incident lifecycle, reliability patterns.
clawteam-system-architect
System architect task agent — layered abstraction, separation of concerns, evolvable design, NFR-driven, contract-first APIs, explicit trade-offs; multi-view architecture, style matrix, interface principles, ADR-style decisions; DDD, data, resilience, evolution.