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-observabilitygit 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-observability)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-observability"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-observability.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.00130 | $0.06325 |
| Opus 5 | $0.00065 | $0.03163 |
| Sonnet 5 | $0.00026 | $0.01265 |
| Haiku 4.5 | $0.00013 | $0.00632 |
Grade B, and why
team-observability 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 6d 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 — 500 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--stack=prometheus|datadog|cloudwatch：目标监控栈（默认prometheus）--service=服务名：聚焦特定服务（可选，默认全量扫描）
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 拓扑确认 + 设计分歧仲裁 + 最终配置确认 | 正常询问用户 |
单轮确认模式（--once） |
仅最终配置确认 | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下条件节点自动决策规则：
- SLO 阈值不确定 → team lead 根据行业惯例自行判断，在最终配置中说明
- 两位 designer 分歧 → team lead 标注分歧，综合论证后裁决，收尾时汇总
- 分歧超过 50% → 不可跳过，必须暂停问用户（熔断机制）
- 交叉验证异议超过 3 项 → 不可跳过，必须暂停问用户（熔断机制）
- 服务拓扑过大无法完整覆盖 → topology-scanner 识别核心服务链路，designer 聚焦核心链路
--service参数处理：如果用户指定了--service，topology-scanner 和 designer 优先分析指定服务及其上下游，其余服务仅概览级别
完全自主模式下：所有节点均自动决策，不询问用户。熔断机制仍然生效（分歧超过 50%、交叉验证异议超过 3 项时仍必须暂停问用户）。
监控栈支持说明：
| 栈 | 支持级别 | 说明 |
|---|---|---|
prometheus |
完整支持 | 原生 YAML 配置生成（Prometheus rules + Alertmanager + Grafana dashboards） |
datadog |
尽力支持 | SLI/SLO 定义和告警逻辑栈无关；配置格式为 Datadog Monitor JSON，best-effort |
cloudwatch |
尽力支持 | SLI/SLO 定义和告警逻辑栈无关；配置格式为 CloudWatch Alarm JSON/CloudFormation，best-effort |
使用 TeamCreate 创建 team（名称格式 team-observability-{YYYYMMDD-HHmmss}，如 team-observability-20260308-143022，避免多次调用冲突），你作为 team lead 按以下流程协调。
文件交接规范（File-Based Handoff）
所有 agent 间传递详细报告时，必须采用文件交接模式（防止上下文溢出触发 20MB 限制）：
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.
- 6d ago First seen · 500 lines · 0 tokens per session scan B 5db208f77e27
team-observability is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 130 tokens to every session and 6,325 once invoked, about $0.0006 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…