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-reportgit 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-report)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-report"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-report.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.00144 | $0.08219 |
| Opus 5 | $0.00072 | $0.04110 |
| Sonnet 5 | $0.00029 | $0.01644 |
| Haiku 4.5 | $0.00014 | $0.00822 |
Grade B, and why
team-report 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 — 639 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--mode=board|team|investor|briefing：报告模式（默认team）--period=1w|2w|1m|1q：报告周期（默认1w）--output=file|stdout：输出方式（默认stdout）--format=markdown|email|slack|ppt-outline：输出格式（默认markdown）--lang=zh|en：输出语言（默认zh中文）
多格式输出支持
--format 参数控制最终报告的呈现格式，适配不同分发场景：
| 格式 | 说明 | 结构 |
|---|---|---|
markdown |
标准 Markdown 格式（默认） | 完整报告 |
email |
邮件摘要格式 | 主题行 + 3-5 要点 + 行动项 |
slack |
Slack 消息格式 | emoji 标记 + 简短段落 + 链接 |
ppt-outline |
PPT 大纲格式 | 每页标题 + 3 要点 + speaker notes |
格式与模式组合建议：
| 模式 | 推荐格式 | 原因 |
|---|---|---|
board |
ppt-outline 或 email |
高管习惯幻灯片或邮件简报 |
team |
markdown 或 slack |
团队常用 Markdown 文档或 Slack 频道 |
investor |
ppt-outline |
投资方演示场景 |
briefing |
slack 或 email |
晨报适合即时推送 |
各格式输出规范：
email 格式：
- 第一行为邮件主题：
[{mode}报告] {project_name} — {period} 总结 - 正文以 3-5 个关键要点开头（bullet points）
- 末尾附"需要关注的行动项"列表
- 总长度控制在屏幕一屏以内
slack 格式：
- 使用 Slack 兼容 mrkdwn 语法
- 状态用 emoji 标记：✅ 完成、🔴 阻塞、⚠️ 风险、📈 上升、📉 下降
- 段落间用分隔线
--- - 关键数字用
*bold*强调 - 末尾附相关链接（如报告完整版文件路径）
ppt-outline 格式：
- 每页输出格式：
## Slide N: {标题} - 每页 3 个要点（bullet points），每点不超过 15 字
- 每页附
> Speaker Notes:块，包含展开说明（2-3 句） - 建议页数：board 5-8 页，investor 6-10 页，team 8-12 页
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 数据源确认 + 草稿选择 + 最终报告确认 | 正常询问用户 |
单轮确认模式（--once） |
仅最终报告确认 | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
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 · 639 lines · 0 tokens per session scan B 03f7524bca6e
team-report is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 144 tokens to every session and 8,219 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…