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-team)<a href="https://agentmods.dev/commands/an8079/take-skills/takes-team"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-team/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-team"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-team.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.00028 | $0.01188 |
| Opus 5 | $0.00014 | $0.00594 |
| Sonnet 5 | $0.00006 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
lyd_team 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/takes-team - 团队协作命令
组建专家团队，通过多 Agent 协作解决复杂问题。支持完整的团队管道：plan → exec → verify → fix。
使用方式
/takes-team "任务描述"
或
组队
团队协作
多 Agent 协作
团队角色
核心角色（自动分配）
| 角色 | Agent | 职责 |
|---|---|---|
| 监督者 | team-lead | 协调团队、跟踪进度、生成报告 |
| 分析师 | analyst | 分析需求、设计方案、拆解任务 |
| 执行者 | executor | 实现功能、编写代码 |
| 验证者 | verifier | 验证结果、检查质量 |
| 批评者 | critic | 挑战方案、识别风险 |
可选角色
| 角色 | Agent | 职责 |
|---|---|---|
| 协调者 | coordinator | 任务分发、优先级管理 |
团队管道
┌─────────────────────────────────────────────────────────┐
│ 团队协作管道 │
├─────────────────────────────────────────────────────────┤
│ │
│ team-plan → team-exec → team-verify │
│ (分析规划) (执行任务) (验证结果) │
│ ↓ ↓ ↓ │
│ └───────────────────┼────────────────┘ │
│ ↓ │
│ team-fix (如需要) │
│ (修复问题，最多3次) │
│ ↓ │
│ ↓ │
│ complete / failed │
└─────────────────────────────────────────────────────────┘
工作流程
1. 团队组建
- 分析任务需求
- 分配团队角色
- 初始化团队状态
2. Plan 阶段
- analyst 分析需求
- 拆解任务列表
- 创建执行计划
3. Exec 阶段
- executor 并行执行任务
- coordinator 分发任务
- team-lead 跟踪进度
4. Verify 阶段
- verifier 验证结果
- critic 挑战方案
- 更新任务状态
5. Fix 循环（如需要）
- 修复失败的任务
- 最多 3 次循环
- 触发 fix-loop
输出内容
团队状态报告
# 团队协作报告
## 团队信息
- 团队名称: {team_name}
- 当前阶段: {phase}
- 迭代次数: {iteration}
## 任务进度
- 总任务数: {tasks_total}
- 已完成: {tasks_completed}
- 失败: {tasks_failed}
- 完成率: {completion_rate}%
## 团队健康
- 总成员: {total_workers}
- 活跃: {active_workers}
- 空闲: {idle_workers}
- 失联: {stale_workers}
## 制品
- 计划文档: {has_plan}
- PRD: {has_prd}
- 验证报告: {has_verify_report}
## Fix 循环
- 当前尝试: {fix_attempt}/{max_attempts}
- 已耗尽: {exhausted}
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 · 176 lines · 28 tokens per session scan A f2bf9ddadf70
lyd_team is a command published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 1,188 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
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.