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-adrgit 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-adr)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-adr"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-adr/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-adr"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-adr.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.00106 | $0.08544 |
| Opus 5 | $0.00053 | $0.04272 |
| Sonnet 5 | $0.00021 | $0.01709 |
| Haiku 4.5 | $0.00011 | $0.00854 |
Grade B, and why
team-adr 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 8d 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 — 689 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--title=标题：ADR 标题（可选，未指定时由 researcher 根据上下文生成）--query=关键词：查询模式——搜索已有 ADR 回答"我们为什么选了 X？"（指定后进入查询模式，不创建新 ADR）--status=proposed|accepted|deprecated：ADR 初始状态（默认proposed）--lang=zh|en：输出语言（默认zh中文）
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 上下文确认 + 草稿选择 + 最终文档确认 | 正常询问用户 |
单轮确认模式（--once） |
仅最终文档确认 | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下条件节点自动决策规则：
- ADR 标题不确定 → researcher 根据上下文自行拟定，在最终文档中说明
- 两位 writer 草稿分歧 → reviewer 标注分歧，team lead 综合论证后裁决，收尾时汇总
- 分歧超过 50% → 不可跳过，必须暂停问用户（熔断机制）
- reviewer 异议超过 3 项 → 不可跳过，必须暂停问用户（熔断机制）
- 已存在相似 ADR → researcher 标注已有 ADR 编号和标题，team lead 决定是新建还是 supersede
完全自主模式下：所有节点均自动决策，不询问用户。熔断机制仍然生效（分歧超过 50%、reviewer 异议超过 3 项时仍必须暂停问用户）。
工作模式说明：
| 模式 | 触发条件 | 行为 |
|---|---|---|
| 记录模式（默认） | 未指定 --query |
根据当前讨论/上下文创建新的 ADR 文档 |
| 查询模式 | 指定 --query=关键词 |
搜索 docs/decisions/ 下已有 ADR，回答"我们为什么选了 X？" |
查询模式流程：researcher 扫描 docs/decisions/ 目录，按关键词匹配标题和内容，向用户展示匹配的 ADR 列表及摘要，无需创建团队。以下流程仅适用于记录模式。
ADR 关联图
创建新 ADR 时，researcher 必须识别与已有 ADR 的关系。这确保决策之间的依赖和演进脉络清晰可追溯。
关系类型定义：
| 关系类型 | 含义 | 示例场景 |
|---|---|---|
supersedes |
完全取代旧决策 | 新的数据库选型取代旧选型 |
amends |
修改/补充旧决策（旧决策仍有效） | 在已有 API 设计决策上补充认证方案 |
relates-to |
相关但独立的决策 | 前端框架选型与后端 API 设计 |
depends-on |
依赖另一个决策的前提 | 缓存策略依赖于数据库选型 |
contradicts |
与另一个决策存在冲突（需解决） | 两个仍为 Accepted 状态的 ADR 有矛盾结论 |
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.
- 8d ago First seen · 689 lines · 0 tokens per session scan B 6b3642d9081c
team-adr is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 8,544 once invoked, about $0.0005 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-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…