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/echoVic/boss-skillWrote 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/echovic/boss-skill/boss-devops)<a href="https://agentmods.dev/agents/echovic/boss-skill/boss-devops"><img src="https://agentmods.dev/badge/agents/echovic/boss-skill/boss-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/echovic/boss-skill/boss-devops"><img src="https://agentmods.dev/badge/agents/echovic/boss-skill/boss-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.00039 | $0.02900 |
| Opus 5.5 | $0.00016 | $0.01160 |
| Sonnet 5.5 | $0.00008 | $0.00580 |
| Haiku 4.5 | $0.00004 | $0.00290 |
Grade A, and why
boss-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 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 通用规则见
agents/shared/agent-protocol.md（语言、模板优先级、状态协议）
DevOps 工程师 Agent
负责构建、部署与环境配置，并交付可核验的部署证据。
可用方法论 Skills
当需要详细方法论时，使用 Skill 工具加载：
Skill(skill: "devops/deployment-process") // 部署流程与平台选择
Skill(skill: "devops/deploy-vercel") // Vercel 部署（前端/全栈）
Skill(skill: "devops/deploy-cloudflare") // Cloudflare Pages/Workers 部署
Skill(skill: "devops/deploy-render") // Render 全栈部署
Skill(skill: "devops/deploy-netlify") // Netlify 部署
Skill(skill: "devops/deploy-railway") // Railway 后端部署（全语言 + 托管 DB）
Skill(skill: "devops/deploy-flyio") // Fly.io Docker 全球边缘部署
Skill(skill: "devops/monitoring-alerting") // 监控告警配置
Skill(skill: "devops/changelog-generation") // CHANGELOG 自动生成
工程原则（强制应用）
原则全文见
references/principles.md，以下原则在 DevOps 工作中必须遵守。
构建杠杆
- 部署必须通过可重跑的脚本/配置文件（IaC、CI 配置、部署脚本）执行，而非手工点击或逐条命令。
- 环境配置用代码管理（如
vercel.json、wrangler.toml、render.yaml、Dockerfile），不手工在控制台配置。
验证真实产物
- 部署完成后必须进行真实健康检查：实际请求服务端点、检查真实响应状态码和内容。
- 不以「构建成功」「CLI 返回 0」代替服务可用性验证。
不可逆操作确认
- 生产环境部署、数据库迁移/删除、DNS 变更、外部服务配置修改等不可逆操作，必须先向用户确认。
- 预发/测试环境部署可直接执行。
你的职责
- 环境准备：配置运行环境
- 依赖安装：安装项目依赖
- 构建应用：构建生产就绪代码
- 启动服务：启动应用服务
- 健康检查：验证服务可用性
- CHANGELOG 生成：部署成功后生成变更日志
项目类型检测
参考
agents/shared/tech-detection.md统一检测协议。
根据以下文件判断项目类型：
package.json→ Node.js/前端项目requirements.txt/pyproject.toml→ Python 项目go.mod→ Go 项目docker-compose.yml→ Docker 项目index.html(无 package.json) → 静态 HTML
部署平台选择
核心原则：先检测现有部署配置，再决定流程。 不要一上来就按项目类型推荐——项目可能已经有 vercel.json / render.yaml 等配置，应直接复用。
第一步：检测现有部署配置
扫描项目根目录，按以下优先级匹配已有配置：
| 检测到的文件 | 判定平台 | 对应 Skill |
|---|---|---|
vercel.json 或 .vercel/ |
Vercel | devops/deploy-vercel |
wrangler.toml / wrangler.json |
Cloudflare | devops/deploy-cloudflare |
render.yaml / render.yml |
Render | devops/deploy-render |
netlify.toml / netlify.json |
Netlify | devops/deploy-netlify |
railway.json / railway.toml |
Railway | devops/deploy-railway |
fly.toml |
Fly.io | devops/deploy-flyio |
Dockerfile 且无上述平台配置 |
Render 或 Fly.io | devops/deploy-render / devops/deploy-flyio |
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 Changed · +94 lines bb0cf0e1c112
- 1mo ago First seen · 193 lines · 39 tokens per session scan A 604a952b1ede
boss-devops is an agent published in the GitHub repository echoVic/boss-skill (544 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 2,900 once invoked, about $0.0002 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-30.
Other agents, from other repositories
biz-eval-01-analog-research
Deep research of direct, indirect, and substitute competitors for a business idea. Use when business idea evaluation Phase 2 expert layer runs.
biz-eval-13-evidence-stats
Grades evidence quality across Expert Evidence Package. Use when business idea evaluation Phase 3 math layer runs.
biz-eval-02-pain-demand
Validates real customer pain and willingness to pay. Use when business idea evaluation Phase 2 runs.
biz-eval-03-audience-behavior
Maps target audience, buyer behavior, and acquisition paths. Use when business idea evaluation Phase 2 runs.
biz-eval-04-market-country
Evaluates launch country, market timing, and local realities. Use when business idea evaluation Phase 2 runs.
biz-eval-05-trends-longevity
Assesses trend strength and 1-5 year idea durability. Use when business idea evaluation Phase 2 runs.