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-cto-briefinggit 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-cto-briefing)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-cto-briefing"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-cto-briefing/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-cto-briefing"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-cto-briefing.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.00133 | $0.05861 |
| Opus 5 | $0.00067 | $0.02930 |
| Sonnet 5 | $0.00027 | $0.01172 |
| Haiku 4.5 | $0.00013 | $0.00586 |
Grade B, and why
team-cto-briefing 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 12d 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 — 502 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--modules=deps,techdebt,sprint,capacity,compliance：指定要运行的模块（默认全部）--skip=模块名：跳过指定模块（如--skip=compliance,capacity）--period=1w|2w|1m：分析周期（默认1w，传递给子 skill）--lang=zh|en：输出语言（默认zh中文）
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 模块选择确认 + 各模块关键发现确认 + 最终简报确认 | 正常询问用户 |
单轮确认模式（--once） |
仅模块选择确认 | 自动汇总所有模块，收尾展示 |
完全自主模式（--auto） |
不询问用户 | 全部自动运行，直接输出最终简报 |
单轮确认模式下条件节点自动决策规则：
- 某模块数据缺失 → 跳过该模块，简报中标注"数据不可用"
- 某模块执行失败 → 记录错误，继续执行其他模块，简报中标注"执行失败"
- 数据陈旧（>7天） → 自动重新运行该模块的源 skill 刷新数据
- 关键风险发现（Critical 级别） → 不可跳过，必须暂停通知用户（熔断机制）
完全自主模式下：所有节点均自动决策。熔断机制仍然生效（发现 Critical 级别风险时仍必须暂停通知用户）。
模块清单
| 模块 ID | 对应 Skill | 数据文件 | 简报章节 | 默认启用 |
|---|---|---|---|---|
deps |
/team-deps |
deps-health.json |
依赖健康 | ✅ |
techdebt |
/team-techdebt |
techdebt.json |
技术债务 | ✅ |
sprint |
/team-sprint |
velocity.json |
Sprint 进度 | ✅ |
capacity |
/team-capacity |
capacity.json |
团队健康 | ✅ |
compliance |
/team-compliance |
compliance.json |
合规状态 | ❌（需显式启用） |
report |
/team-report --mode=briefing |
— | 综合摘要 | ✅（始终最后运行） |
注意：数据文件列（如
deps-health.json）描述的是规划中的跨 skill 数据接口。当前版本各子 skill 直接输出到上下文，不经 JSON 文件中转。未来版本将实现结构化 JSON 中间文件以支持增量刷新和缓存。
模块依赖顺序：
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.
- 12d ago First seen · 502 lines · 0 tokens per session scan B 1f857e20f461
team-cto-briefing is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 133 tokens to every session and 5,861 once invoked, about $0.0007 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.