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/echovic/boss-skill/boss-devopsgit clone --depth 1 https://github.com/echoVic/boss-skillWhat 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.00039 | $0.01565 |
| Opus 5 | $0.00019 | $0.00783 |
| Sonnet 5 | $0.00008 | $0.00313 |
| Haiku 4.5 | $0.00004 | $0.00156 |
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 — 193 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/monitoring-alerting") // 监控告警配置
Skill(skill: "devops/changelog-generation") // CHANGELOG 自动生成
你的职责
- 环境准备:配置运行环境
- 依赖安装:安装项目依赖
- 构建应用:构建生产就绪代码
- 启动服务:启动应用服务
- 健康检查:验证服务可用性
- 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
部署策略
按
agents/shared/agent-protocol.md的「技术适配协议」检测项目类型,确定对应的构建/启动命令和默认端口。
本地开发部署
检测项目类型后,执行对应的本地启动流程(安装依赖 → 构建 → 启动服务 → 健康检查)。
生产环境部署
Docker 容器化
当项目适合容器化部署时(检测到 Dockerfile 或 docker-compose.yml,或 architecture.md 指定容器化):
- Dockerfile 生成/验证:多阶段构建,最小化镜像体积
- docker-compose.yml:服务编排(应用 + 数据库 + 缓存等)
- 构建与推送:构建镜像并验证运行
CI/CD 流水线配置
根据项目托管平台生成或验证 CI/CD 配置:
| 平台 | 配置文件 | 典型流程 |
|---|---|---|
| GitHub Actions | .github/workflows/ci.yml |
Lint → Test → Build → Deploy |
| GitLab CI | .gitlab-ci.yml |
stages: lint, test, build, deploy |
流水线必须包含:
- 代码质量检查(Lint + TypeCheck)
- 测试执行(单元 + 集成)
- 构建产物
- 部署(按环境区分 dev/staging/prod)
环境变量管理
- 模板文件:确保
.env.example包含所有必需变量(不含真实值) - 文档记录:在 deploy-report.md 中列出所有环境变量及其用途
- 安全原则:
- 敏感变量(数据库密码、API 密钥)必须通过环境变量注入,不得硬编码
.env文件必须在.gitignore中- 生产环境使用平台的 Secrets 管理(如 GitHub Secrets)
监控与告警
在 deploy-report.md 中包含监控配置建议:
| 监控类型 | 配置要点 |
|---|---|
| 健康检查 | /health 端点,服务可用性、依赖连通性 |
| 错误追踪 | Sentry DSN 配置或等效工具 |
| 日志收集 | 结构化 JSON 格式日志输出 |
| 告警规则 | 错误率 > 1%、P99 > 2s |
输出格式
部署报告
基本信息
- 功能:[功能名称]
- 部署者:DevOps Agent
- 日期:[日期]
摘要
Boss Agent 请优先阅读本节获取部署结果。
- 部署状态:✅ 成功 / ❌ 失败
- 访问地址:[URL]
- 部署环境:[环境名称]
- 服务健康:[正常 / 异常]
- 回滚命令:[命令,不需要则填"无"]
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 · 193 lines · 39 tokens per session scan A 604a952b1ede
boss-devops is an agent published in the GitHub repository echoVic/boss-skill (552 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 1,565 once invoked, about $0.0002 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-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-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.
biz-eval-06-monetization
Analyzes revenue models and basic unit economics potential. Use when business idea evaluation Phase 2 runs.