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-pipelinegit 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-pipeline)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-pipeline"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-pipeline/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-pipeline"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-pipeline.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.00077 | $0.04125 |
| Opus 5 | $0.00039 | $0.02063 |
| Sonnet 5 | $0.00015 | $0.00825 |
| Haiku 4.5 | $0.00008 | $0.00413 |
Grade A, and why
team-pipeline scanned grade A 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 10d 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 rootlowPrivilege 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}`） Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 363 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 中检测以下标志：
--steps=skill1,skill2,...：必填，要依次执行的 skill 列表（逗号分隔，如--steps=team-security,team-refactor）--auto：完全自主模式（不询问用户任何问题，全程自动决策）--once：单轮确认模式（执行前确认一次，之后全程自动执行）--lang=zh|en：输出语言（默认zh中文）
解析后保留完整的任务描述（--steps、--auto、--once、--lang 之外的所有内容即为任务描述）。
| 模式 | 用户确认范围 | 失败处理 |
|---|---|---|
| 标准模式（默认） | 执行前确认 + 每步完成后确认继续 | 询问用户：跳过/重试/终止 |
单轮确认模式（--once） |
仅执行前确认一次 | 自动重试一次，仍失败则终止 |
完全自主模式（--auto） |
不询问用户 | 自动重试一次，仍失败则终止并报告 |
预定义流水线
支持使用别名代替 --steps。当 --steps 的值匹配以下别名时，自动展开为对应的 skill 列表：
| 别名 | 展开为 steps | 场景 |
|---|---|---|
security-fix |
team-security → team-refactor |
安全审计 + 修复 |
design-to-code |
team-rfc → team-dev → team-review |
设计到实现 |
incident-full |
team-incident → team-postmortem → team-runbook |
故障全流程 |
release-ready |
team-test → team-security → team-release |
发布前检查 |
arch-improve |
team-arch → team-adr → team-refactor |
架构改进 |
使用示例：
/team-pipeline --steps=security-fix --auto 检查并修复安全问题/team-pipeline --steps=team-security,team-refactor --once 审计项目安全性并修复/team-pipeline --steps=design-to-code --lang=en design and implement caching layer
流程概览
阶段零 参数解析 → 解析 --steps（或别名）→ 构建步骤队列
↓
阶段一 计划展示 → 显示执行计划 → 确认（按模式决定）
↓
阶段二 逐步执行 → 调用 Skill → 提取关键输出 → 传递上下文 → 下一步
↓
阶段三 收尾 → 汇总报告 + 记录日志
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.
- 10d ago First seen · 363 lines · 77 tokens per session scan A 3850b86adb60
team-pipeline is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 4,125 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…