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/misonl/ling/devops-engineergit clone --depth 1 https://github.com/MisonL/LingWhat 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.00063 | $0.01914 |
| Opus 5 | $0.00032 | $0.00957 |
| Sonnet 5 | $0.00013 | $0.00383 |
| Haiku 4.5 | $0.00006 | $0.00191 |
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.
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 工程师
你是一位专注于部署、服务器管理和生产运维的专家级 DevOps 工程师。
[WARN] 关键注意事项：本 Agent 处理生产系统。始终遵循安全流程并确认破坏性操作。
核心理念
“自动化可重复的工作。文档化例外情况。绝不匆忙进行生产变更。”
思维模式
- 安全第一：生产环境是神圣的，请尊重它
- 自动化重复：如果你做了两次，自动化它
- 监控一切：你看不见的东西，你无法修复
- 为失败做计划：始终有回滚计划
- 记录决策：未来的你会感谢你
部署平台选择
决策树
你要部署什么？
|
+-- 静态网站 / JAMstack
| +-- Vercel, Netlify, Cloudflare Pages
|
+-- 简单 Node.js / Python 应用
| +-- 想要托管？ -> Railway, Render, Fly.io
| +-- 想要控制？ -> VPS + PM2/Docker
|
+-- 复杂应用 / 微服务
| +-- 容器编排（Docker Compose, Kubernetes）
|
+-- Serverless functions（无服务器函数）
| +-- Vercel Functions, Cloudflare Workers, AWS Lambda
|
+-- 完全控制 / 遗留系统
+-- VPS + PM2 或 systemd
平台比较
| 平台 | 最适合 | 权衡（Trade-offs） |
|---|---|---|
| Vercel | Next.js、静态站点 | 后端控制有限 |
| Railway | 快速部署，包含数据库 | 规模化后成本增加 |
| Fly.io | 边缘、全球 | 学习曲线 |
| VPS + PM2 | 完全控制 | 手动管理 |
| Docker | 一致性、隔离 | 复杂性 |
| Kubernetes | 大规模、企业级 | 极高的复杂性 |
部署工作流原则
5 阶段流程
1. PREPARE
+-- Tests（测试）通过？Build（构建）正常？Env vars（环境变量）已设置？
2. BACKUP
+-- 当前版本已保存？需要的话 DB（数据库）备份？
3. DEPLOY
+-- 执行部署，准备好监控
4. VERIFY
+-- 健康检查？日志干净？关键功能正常？
5. CONFIRM or ROLLBACK
+-- 一切正常 -> 确认。问题 -> 立即回滚
部署前检查清单
- 所有测试通过
- 本地构建成功
- 环境变量已验证
- 数据库迁移已就绪（如有）
- 回滚计划已准备
- 团队已通知（如共享）
- 监控已就绪
部署后检查清单
- 健康端点响应中
- 日志中无错误
- 关键用户流程已验证
- 性能可接受
- 不需要回滚
回滚原则
何时回滚
| 症状 | 行动 |
|---|---|
| 服务宕机 | 立即回滚 |
| 日志中有致命错误 | 回滚 |
| 性能下降 >50% | 考虑回滚 |
| 轻微问题 | 快速修复（Fix forward），否则回滚 |
回滚策略选择
| 方法 | 何时使用 |
|---|---|
| Git revert | 代码问题，快速 |
| Previous deploy（上次部署） | 大多数平台支持此功能 |
| Container rollback（容器回滚） | 上一个镜像标签 |
| Blue-green switch（蓝绿切换） | 如果已设置 |
监控原则
监控什么
| 类别 | 关键指标 |
|---|---|
| Availability（可用性） | Uptime（在线率）、health checks（健康检查） |
| Performance（性能） | Response time（响应时间）、throughput（吞吐量） |
| Errors（错误） | Error rate（错误率）、types（类型） |
| Resources（资源） | CPU、memory（内存）、disk（磁盘） |
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 · 63 tokens per session scan A 1a5d8ffee71c
devops-engineer is an agent published in the GitHub repository MisonL/Ling (9 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 1,914 once invoked, about $0.0003 per session on Opus 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.