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/commands/echovic/boss-skill/boss-ship)<a href="https://agentmods.dev/commands/echovic/boss-skill/boss-ship"><img src="https://agentmods.dev/badge/commands/echovic/boss-skill/boss-ship/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/commands/echovic/boss-skill/boss-ship"><img src="https://agentmods.dev/badge/commands/echovic/boss-skill/boss-ship.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.00050 | $0.00557 |
| Opus 5.5 | $0.00020 | $0.00223 |
| Sonnet 5.5 | $0.00010 | $0.00111 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
boss:ship 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.
What it actually says
/boss:ship — 单环节：构建部署（DevOps）
/boss:ship 是 Boss 流水线的部署环节独立入口。以 DevOps 身份完成构建、部署、健康检查，运行上线前门禁（Gate 2），产出 deploy-report.md。
对标 gstack
/ship。Boss 版本在部署前强制跑 Gate 2（Lighthouse / API P99），门禁不过不宣布上线成功。
适合 / 不适合
适合 /boss:ship |
不适合 |
|---|---|
| 已过测试、要构建部署 | 还没过 QA（先 /boss:qa） |
| 补一份可追溯部署报告 | 只是本地跑一下（直接 npm run dev） |
执行步骤
- 读取
SKILL.md不变量与references/quality-gate.md（Gate 2）。 - 前置检查：确认
qa-report.md存在且 Gate 1 已过（无则提示先跑/boss:qa）。 - 读取
agents/boss-devops.md与skills/devops/deployment-process/SKILL.md、skills/devops/monitoring-alerting/SKILL.md、skills/devops/changelog-generation/SKILL.md。 - 以 DevOps 身份执行构建 + 部署 + 健康检查，产出
deploy-report.md（模板templates/deploy-report.md.template）。 - 运行 Gate 2：
boss runtime evaluate-gates <feature> gate-2。无 CLI 时按references/no-cli-fallback.md记录到 STATE.md。 - 收尾：
boss runtime generate-summary <feature>。输出：部署 URL、健康检查、门禁结果、changelog。
用法
/boss:ship # 部署当前项目
/boss:ship user-auth # 部署已有 feature
选项
| 参数 | 说明 |
|---|---|
--lang <zh|en> |
部署报告语言（默认 zh） |
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 · 41 lines · 50 tokens per session scan A 2098701c0f92
boss:ship is a command published in the GitHub repository echoVic/boss-skill (543 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 557 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 commands, from other repositories
pull
Refreshes local project state from a linked Supabase project or branch in one step, instead of running config pull, db pull, migration fetch, and functions download individually. It runs four steps, always in this order: pull config into supabase/config.toml, optionally fetch the remote migration history table into…
secrets
Provides tools for managing environment variables and secrets for your Supabase project.
deploy-config
Detect the project's Vercel deployment shape and generate or validate a tailored vercel.json.
coolify-debug
Diagnose Coolify deployment issues.
wa-guardrails
Generate preventive Well-Architected guardrails — AWS Config rules, Service Control Policies, permission boundaries, CloudWatch alarms, and IaC policy checks (CDK Aspects, cfn-guard, OPA/Sentinel) — so a workload stays aligned with Well-Architected best practices over time instead of being assessed once.
cost-optimization-review
Run a pillar-scoped Well-Architected review focused on the Cost Optimization pillar.