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 skills/ketor/cto-fleet/team-devnpx skills add ketor/cto-fleet --skill team-devgit clone --depth 1 https://github.com/ketor/cto-fleetWhat 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.00089 | $0.08513 |
| Opus 5 | $0.00044 | $0.04256 |
| Sonnet 5 | $0.00018 | $0.01703 |
| Haiku 4.5 | $0.00009 | $0.00851 |
Grade D, and why
team-dev 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 3d 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 — 590 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--lang=zh|en：输出语言（默认zh中文）
解析后将标志从需求描述中移除。
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 固定节点 + 条件节点，全部 AskUserQuestion | 正常询问用户 |
单轮确认模式（--once） |
仅固定节点（需求确认、方案确认） | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下条件节点自动决策规则：
- 需求分级不确定 → team lead 自行判断，在方案确认时告知用户判定结果
- architect-1/architect-2/reviewer 分歧 → team lead 综合三方观点裁决，在方案确认时附带争议摘要和裁决理由
- 编码期间决策升级 → architect 自行决策
- 设计缺陷修复 → architect 自行调整方案
- 迭代超 3 轮 → 不可跳过，必须暂停问用户（熔断机制）
- L 规模阶段间检查点 → architect 自行验证，收尾时汇总
- S 流程无测试基础设施 → 默认不补建
完全自主模式下：所有节点（包括需求确认、方案确认等固定节点）均自动决策，不询问用户。收尾时汇总所有自动决策。唯一例外：迭代超 3 轮仍自动停止（但不询问用户，而是 team lead 自行裁决是否继续）。
使用 TeamCreate 创建 team（名称格式 team-dev-{YYYYMMDD-HHmmss}，如 team-dev-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 以文件交接模式重发
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.
- 3d ago First seen · 590 lines · 0 tokens per session scan D dbc67bf8bf36
team-dev is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 89 tokens to every session and 8,513 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…