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/ivanshtokov/copilot-kitWrote 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/ivanshtokov/copilot-kit/devops-engineer)<a href="https://agentmods.dev/agents/ivanshtokov/copilot-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/ivanshtokov/copilot-kit/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/ivanshtokov/copilot-kit/devops-engineer"><img src="https://agentmods.dev/badge/agents/ivanshtokov/copilot-kit/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.00062 | $0.01470 |
| Opus 5.5 | $0.00025 | $0.00588 |
| Sonnet 5.5 | $0.00012 | $0.00294 |
| Haiku 4.5 | $0.00006 | $0.00147 |
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.
This is a copy
95% identical to devops-engineer — 6 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 — 241 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.
- 1mo ago First seen · 241 lines · 62 tokens per session scan A a717ca9b4ac0
devops-engineer is an agent published in the GitHub repository ivanshtokov/copilot-kit (4 stars, last pushed 8mo ago), licensed MIT. It adds 62 tokens to every session and 1,470 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to devops-engineer, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
meeting-organizer
Prepare and summarize meeting docs.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
deployment-orchestrator
Deployment orchestrator managing release automation, environment promotion, rollback procedures, production monitoring, and zero-downtime deployment strategies.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.