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 agentmods add skills/ketor/cto-fleet/team-interviewnpx skills add ketor/cto-fleet --skill team-interviewgit 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-interview)<a href="https://agentmods.dev/skills/ketor/cto-fleet/team-interview"><img src="https://agentmods.dev/badge/skills/ketor/cto-fleet/team-interview.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 | $0.00125 | $0.08847 |
| Opus 5 | $0.00063 | $0.04424 |
| Sonnet 5 | $0.00025 | $0.01769 |
| Haiku 4.5 | $0.00013 | $0.00885 |
Grade B, and why
team-interview 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 5d 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 — 668 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：单轮确认模式（将所有需要确认的问题合并为一轮提问，确认后全程自动执行）--role=backend|frontend|fullstack|devops|sre：目标岗位（默认fullstack）--level=junior|mid|senior|staff：候选人级别（默认mid）--count=N：题目数量（默认5）
解析后将标志从项目路径或描述中移除。
| 模式 | 用户确认范围 | 条件节点处理 |
|---|---|---|
| 标准模式（默认） | 代码库分析确认 + 题目内容确认 | 正常询问用户 |
单轮确认模式（--once） |
仅最终题目集确认 | 自动决策 + 收尾汇总 |
完全自主模式（--auto） |
不询问用户 | 全部自动决策，收尾汇总所有决策 |
单轮确认模式下条件节点自动决策规则：
- 代码库分析有疑问 → team lead 根据项目结构自行判断，在最终输出中说明
- 两位 designer 出题方向重叠 → team lead 去重合并后裁决，收尾时汇总
- 重叠超过 50% → 不可跳过，必须暂停问用户（熔断机制）
- reviewer 判定题目有重大问题（泄露敏感信息/无法在面试时间内完成/评分标准模糊） → 不可跳过，必须暂停问用户（熔断机制，单轮确认模式和完全自主模式均适用）
完全自主模式下：所有节点均自动决策，不询问用户。熔断机制仍然生效——触发熔断条件时是唯一会暂停询问用户的情况。
- 项目过大无法完整分析 → analyst 识别核心模块，聚焦高价值面试场景
岗位与级别说明：
| 岗位 | 侧重领域 |
|---|---|
backend |
后端架构、API 设计、数据存储、并发处理、性能优化 |
frontend |
前端架构、组件设计、状态管理、性能优化、用户体验 |
fullstack |
全栈覆盖，前后端均衡 |
devops |
CI/CD、基础设施、容器化、监控告警、自动化运维 |
sre |
可靠性工程、故障排查、性能调优、容量规划、事故响应 |
| 级别 | 题目难度与考察深度 |
|---|---|
junior |
基础实现能力、代码风格、简单模块开发、常见 bug 定位 |
mid |
模块设计能力、跨模块数据流理解、性能基础优化、Code Review 能力 |
senior |
系统设计能力、架构 trade-off 分析、复杂问题拆解、技术决策论证 |
staff |
跨系统架构、技术战略、大规模重构方案、团队技术规范制定 |
使用 TeamCreate 创建 team（名称格式 team-interview-{YYYYMMDD-HHmmss}，如 team-interview-20260308-143022，避免多次调用冲突），你作为 team lead 按以下流程协调。
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.
- 5d ago First seen · 668 lines · 0 tokens per session scan B 0d4149073ffb
team-interview is a skill published in the GitHub repository ketor/cto-fleet (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 125 tokens to every session and 8,847 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
miniapp
Build a tiny interactive HTML playground only when someone asks to see, play with, or step through a mechanism.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
best-practices
Searchable knowledge base of 152+ programming best practices across 30+ languages and frameworks. BM25-powered search over curated resources from industry leaders (Google, Airbnb, Uber, Mozilla, Shopify, OWASP).