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 skills add ketor/cto-fleet --skill team-releasegit clone --depth 1 https://github.com/ketor/cto-fleetWrote 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/skills/ketor/cto-fleet/team-release)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-release"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-release.svg" alt="Measured on agentmods" 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.00106 | $0.07162 |
| Opus 5 | $0.00053 | $0.03581 |
| Sonnet 5 | $0.00021 | $0.01432 |
| Haiku 4.5 | $0.00011 | $0.00716 |
Grade B, and why
team-release scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- 目录路径：`/tmp/{team-name}/`（team lead 在 TeamCreate 后执行 `mkdir -p /tmp/{team-name} && chmod 700 /tmp/{team-name}`） How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble (run first)
_UPD=$(~/.claude/skills/cto-fleet/bin/cto-fleet-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/cto-fleet/cto-fleet-upgrade/SKILL.md and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If JUST_UPGRADED <from> <to>: tell user "Running cto-fleet v{to} (just updated!)" and continue.
参数解析：从 $ARGUMENTS 中检测以下标志：
--auto：完全自主模式（不询问用户任何问题，全程自动决策）--once：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--type=major|minor|patch|hotfix：发布类型（默认根据变更内容自动推断）--from=tag/commit：变更起始点（默认为上一个 tag）--lang=zh|en：输出语言（默认zh中文）
解析后将标志从发布描述中移除。
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 确认发布范围 + 确认发布执行 | 正常询问用户 |
单轮确认模式（--once） |
仅确认发布执行 | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下条件节点自动决策规则：
- 发布类型不确定 → team lead 根据变更内容自动推断，在发布确认时告知用户推断结果
- validator-1/validator-2 发现问题 → team lead 综合两份验证报告裁决，在发布确认时附带问题摘要
- 风险评估为 Medium → 继续流程，在发布确认时高亮风险项
- 风险评估为 High/Critical → 不可跳过，必须暂停问用户（熔断机制）
- 检查清单有项目未通过 → 不可跳过，必须暂停问用户（熔断机制，单轮确认模式和完全自主模式均适用）
完全自主模式下：所有节点均自动决策，不询问用户。熔断机制仍然生效——触发熔断条件时是唯一会暂停询问用户的情况。
发布类型表
| Type | Version Change | 风险等级 | 额外检查 |
|---|---|---|---|
| major | X.0.0 | High | Breaking change 逐项审查，migration plan 必须提供 |
| minor | x.Y.0 | Medium | 功能完整性检查，对照 milestone/issue 验证 |
| patch | x.y.Z | Low | 修复项逐一验证，确认无副作用 |
| hotfix | x.y.Z+1 | Critical | 最小变更审查，快速通道，仅验证修复目标 |
Hotfix 快速通道：当 --type=hotfix 时，流程大幅精简：
- 阶段一：仅启动 scanner（不启动 validator-1/validator-2），scanner 仅扫描修复相关 commit
- 阶段二：跳过完整风险评估，仅检查变更规模和测试覆盖两个维度
- 阶段三：checker 执行精简清单（仅 #1 CI 全绿、#2 版本号、#3 Changelog、#6 回滚方案、#9 依赖安全）
- 阶段四：正常收尾
使用 TeamCreate 创建 team（名称格式 team-release-{YYYYMMDD-HHmmss}，如 team-release-20260311-143022，避免多次调用冲突），你作为 team lead 按以下流程协调。
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.
- 7d ago First seen · 507 lines · 0 tokens per session scan B 92f6de52cfb6
team-release is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 7,162 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.