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-debugnpx skills add ketor/cto-fleet --skill team-debuggit 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.00087 | $0.07694 |
| Opus 5 | $0.00044 | $0.03847 |
| Sonnet 5 | $0.00017 | $0.01539 |
| Haiku 4.5 | $0.00009 | $0.00769 |
Grade B, and why
team-debug scanned grade B 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}`） Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- 脚本结构：① 设置前置条件（启动服务/准备数据） → ② 执行触发操作（curl/CLI 命令/API 调用） → ③ 检查结果并输出 PASS/FAIL How it starts
The opening of the file, as written. The whole thing — 522 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中文）
解析后将标志从 bug 描述中移除。
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | Bug 分析确认、根因确认、修复方案确认 | 正常询问用户 |
单轮确认模式（--once） |
仅修复方案确认（因为修复有风险） | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下条件节点自动决策规则：
- Bug 分析不确定 → team lead 自行判断，在修复方案确认时告知用户判定结果
- analyzer-1/analyzer-2 根因分歧 → team lead 综合两方分析裁决，在根因确认时附带分歧摘要和裁决理由
- 修复后验证失败 → fixer 自行调整修复方案重试
- 分歧度 > 50% → 不可跳过，必须暂停问用户（熔断机制）
- 修复后验证失败超 3 轮 → 不可跳过，必须暂停问用户（熔断机制）
完全自主模式下：所有节点（包括 Bug 分析确认、根因确认、修复方案确认等）均自动决策，不询问用户。收尾时汇总所有自动决策。唯一例外：验证失败超 3 轮仍自动停止（但不询问用户，而是 team lead 自行裁决是否继续）。
使用 TeamCreate 创建 team（名称格式 team-debug-{YYYYMMDD-HHmmss}，如 team-debug-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 · 522 lines · 0 tokens per session scan B fd6372f37dee
team-debug is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 7,694 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-integration
Run all three agent integration phases sequentially: research, write-tests, and implement using E2E-first TDD (unit tests written last). For individual phases, use /agent-integration:research, /agent-integration:write-tests, or /agent-integration:implement. Use when the user says "integrate agent", "add agent…
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
css-design-tdd
Test-driven CSS design system modifications. Run checks before/after CSS changes to verify token usage, variable definitions, fallbacks, and consistency. Use when modifying CSS tokens, fixing design inconsistencies, or auditing CSS architecture.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
refine-plan
Iteratively refine development plans using TDD methodology. Ensures plans are clear, actionable, and include red-green-refactor cycles with proper test coverage.