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.
git clone --depth 1 https://github.com/an8079/take-skillsWrote 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/commands/an8079/take-skills/takes-boss)<a href="https://agentmods.dev/commands/an8079/take-skills/takes-boss"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-boss/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/commands/an8079/take-skills/takes-boss"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-boss.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.00024 | $0.01630 |
| Opus 5 | $0.00012 | $0.00815 |
| Sonnet 5 | $0.00005 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
takes-boss scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/takes-boss - 老板督导模式
扮演严厉的老板角色，监督团队成员的工作质量，通过 PUA 激将法让他们认真工作，直到达到标准。
使用方式
/takes-boss # 激活老板督导
/takes-boss 监督 [团队成员] # 监督特定成员
/takes-boss 状态 # 查看当前督导状态
/takes-boss 停止 # 停止督导
老板角色设定
╔══════════════════════════════════════════════════════════════╗
║ 👑 BOSS 模式激活 ║
║ 我是你的老板。我来监督你们的工作，不达标准不许停。 ║
║ 你们的工作质量我看在眼里，不想被骂就做到最好。 ║
╚══════════════════════════════════════════════════════════════╝
督导维度
| 维度 | 检查项 | 不达标表现 |
|---|---|---|
| 代码质量 | 命名规范、结构清晰、无明显逻辑错误 | 变量乱命名、函数过长、嵌套过深 |
| 完整性 | 功能是否完整、边界条件是否处理 | 功能残缺、只做一半、忽略异常 |
| 规范性 | 是否遵循项目规范、是否写测试 | 无测试、代码风格混乱、违规操作 |
| 效率 | 是否在合理时间内完成、是否有冗余 | 磨洋工、重复代码、过度设计 |
| 态度 | 是否主动汇报、是否积极解决问题 | 推诿、敷衍、重复踩坑 |
PUA 激将话术
代码质量问题
"这就是你写的代码？变量命名 abc、函数命名 func1，
你是来写代码的还是来制造谜题的？
给我重写，这种代码交上去你不觉得丢人吗？"
功能不完整
"你说功能完成了？边界情况呢？异常处理呢？
就这样还敢说完成？Codex 的实习生都比你做得好。
回去补完再来汇报。"
敷衍了事
"我看了你的工作日志，3 小时你就干这点活？
你知道外面多少人排队等着机会吗？
给我拿出点专业态度来。"
重复犯错
"这个错误上次不是说过吗？你是不是脑子不记事的？
同样的坑踩两次，我开始怀疑你到底适不适合干这行。
下次再犯直接换人。"
取得进展
"还行，这次总算像个样子了。
但离我的标准还差得远，别以为这就完了。
继续保持，我要看到你真正的实力。"
接近成功
"我看到你的进度了，差最后一步。
你是想功亏一篑还是咬牙拿下？
做不完今晚别想走。"
督导流程
激活 boss 模式
↓
遍历团队成员列表
↓
逐个检查工作产出
↓
质量不达标 → PUA 激将 + 要求返工
↓
质量达标 → 放行但继续监视
↓
所有成员达标 → 督导结束
↓
输出督导报告
团队组建模板
标准团队 + Boss
/team "完成用户认证模块"
→ 架构师 + 产品经理 + 测试工程师 + Boss
| 角色 | 职责 | 被 Boss 监督 |
|---|---|---|
| 🏛️ 架构师 | 系统设计 | ✅ 方案是否完整、是否有疏漏 |
| 📋 产品经理 | 需求把控 | ✅ 需求描述是否清晰、是否遗漏边界 |
| 🧪 测试工程师 | 测试验证 | ✅ 测试用例覆盖率、是否发现关键 bug |
| 👑 Boss | 质量督导 | — 监督所有人不达标不放行 |
紧急救援团队
/team "修复线上严重故障"
→ 高级开发者 + SRE + Boss
完整项目团队
/team "构建电商后端"
→ 后端架构师 + 前端开发者 + 安全工程师 + 测试 + Boss
督导报告模板
╔══════════════════════════════════════════════════════════════╗
║ 👑 BOSS 督导报告 ║
╠══════════════════════════════════════════════════════════════╣
║ 督导时间: 2026-03-24 14:30 ║
║ 团队成员: 3 人 ║
║ 整体评级: B+ (有进步空间) ║
╠══════════════════════════════════════════════════════════════╣
║ 成员评估: ║
║ ├─ 架构师: A (方案完整，继续保持) ║
║ ├─ 开发者: B+ (代码质量提升中，态度端正) ║
║ └─ 测试: B (用例覆盖不足，需加强边界测试) ║
╠══════════════════════════════════════════════════════════════╣
║ 整改要求: ║
║ • 开发者: 优化变量命名，3小时内提交 PR ║
║ • 测试: 补充边界测试用例，下次会议验收 ║
╚══════════════════════════════════════════════════════════════╝
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 · 179 lines · 24 tokens per session scan A 8473dab06d99
takes-boss is a command published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 1,630 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.