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-reviewgit 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-review)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-review"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-review/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/skills/ketor/cto-fleet/team-review"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-review.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.00118 | $0.07177 |
| Opus 5 | $0.00059 | $0.03589 |
| Sonnet 5 | $0.00024 | $0.01435 |
| Haiku 4.5 | $0.00012 | $0.00718 |
Grade D, and why
team-review scanned grade D with 2 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 9d 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}`） Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
关闭所有 teammate，执行 `rm -rf /tmp/{team-name}` 清理工作目录，用 TeamDelete 清理 team。 How it starts
The opening of the file, as written. The whole thing — 540 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--focus=area1,area2：聚焦审查领域（可选，默认全面审查）--lang=zh|en：输出语言（默认zh中文）
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 每轮审查报告确认 + 修复方案确认 | 正常询问用户 |
单轮确认模式（--once） |
仅首轮审查报告确认 + 收尾汇总 | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下自动决策规则：
- 审查发现分级不确定 → 对应 reviewer 自行判断，首轮报告中说明
- 修复方案有争议 → 采纳对应维度 reviewer 的建议
- 迭代超 3 轮仍未达标 → 不可跳过，必须暂停问用户（熔断机制）
- 修复引入新问题 → fixer 自行回退并重新修复
- 双 reviewer 评分尺度差异过大（同维度校准差 > 2 分） → 不可跳过，必须暂停问用户（熔断机制）
完全自主模式下：所有节点均自动决策，不询问用户。熔断机制仍然生效（迭代超 3 轮、评分尺度差异过大时仍必须暂停问用户）。
使用 TeamCreate 创建 team（名称格式 team-review-{YYYYMMDD-HHmmss}，如 team-review-20260308-143022，避免多次调用冲突），你作为 team lead 按以下流程协调。
文件交接规范（File-Based Handoff）
所有 agent 间传递详细报告时，必须采用文件交接模式（防止上下文溢出触发 20MB 限制）：
- 写入文件：将完整报告写入团队工作目录：
- 目录路径：
/tmp/{team-name}/（team lead 在 TeamCreate 后执行mkdir -p /tmp/{team-name} && chmod 700 /tmp/{team-name}） - 单个文件 ≤ 2000 行；超大报告拆分为 summary + details 文件
- 目录路径：
- 发送引用：通过 SendMessage 仅发送（≤500 字符）：
- 文件路径（1 行）
- 关键摘要（含核心指标/发现/评分）
- 按需读取：接收方使用 Read 按需读取文件，发送方不内联完整内容
- 路径转发：team lead 转发报告时只转发文件路径 + 摘要，不 Read 后再 SendMessage
- 遵从校验：team lead 收到超 1000 字符且不含
/tmp/team-路径前缀的消息时，要求 agent 以文件交接模式重发
文件命名规范：
| 角色输出 | 文件名 |
|---|---|
| Scanner 报告 | scanner-report.md |
| Reviewer-N 第R轮 | reviewer-{N}-round-{R}.md |
| 合并报告第R轮 | merged-report-round-{R}.md |
| 根因分组 | root-cause-groups-round-{R}.md |
| Fixer 第R轮 | fixer-round-{R}.md |
| Tester 第R轮 | tester-round-{R}.md |
| Architect-N 方案 | architect-{N}-design.md |
| 任务拆解 | task-breakdown.md |
| Coder-N 任务T | coder-{N}-task-{T}.md |
| 审查任务T | review-task-{T}.md |
| 集成测试第R轮 | integration-test-round-{R}.md |
| 最终报告 | final-report.md |
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.
- 9d ago First seen · 540 lines · 0 tokens per session scan D d03b87310883
team-review is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 118 tokens to every session and 7,177 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…