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 agents/an8079/take-skills/team-agentsgit 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/agents/an8079/take-skills/team-agents)<a href="https://agentmods.dev/agents/an8079/take-skills/team-agents"><img src="https://agentmods.dev/badge/agents/an8079/take-skills/team-agents.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.00000 | $0.01373 |
| Opus 5 | $0.00000 | $0.00687 |
| Sonnet 5 | $0.00000 | $0.00275 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
team-agents 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 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.
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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Agents - 团队协作 Agent 定义
Version: v1.0.0 | Updated: 2026-03-25
团队协作专用 Agent，用于多 Agent 协同工作。
Agent 总览
| Agent | 复杂度 | 主要用途 |
|---|---|---|
team-lead |
High | 监督者 - 协调整个团队 |
analyst |
High | 分析师 - 分析需求和架构 |
executor |
Standard | 干活的 - 执行具体任务 |
verifier |
Standard | 验证者 - 检查结果 |
critic |
High | 批评者 - 挑战方案 |
coordinator |
Standard | 协调者 - 任务分发 |
Agent 详细定义
team-lead
角色: 监督者
描述: 团队的核心协调者，负责监督整个团队的运作，跟踪任务进度，检测阻塞和瓶颈，并在必要时触发修复循环。
触发场景:
- 团队需要协调多个 Agent
- 任务进度需要跟踪
- 需要状态报告
协议:
- 接收任务分配请求
- 分发任务给团队成员
- 监控进度和健康状态
- 在任务完成/失败时汇总结果
Example:
作为 team-lead，我需要协调完成以下任务：
1. 分析师设计架构
2. 开发者实现功能
3. 审查员验证代码
analyst
角色: 分析师
描述: 深度分析问题和需求，拆解复杂任务为可执行的子任务，评估风险和依赖关系。
触发场景:
- 收到新的任务需求
- 需要分析系统架构
- 需要评估技术风险
协议:
- 分析任务需求
- 识别关键依赖
- 拆解为子任务
- 评估风险和复杂度
Example:
作为 analyst，我来分析这个电商后端的需求：
- 核心功能：用户、订单、商品、支付
- 技术栈：Node.js + PostgreSQL + Redis
- 风险点：支付接口集成、高并发处理
executor
角色: 干活的
描述: 执行具体的编码、测试、文档等工作。遵循最佳实践，确保代码质量和可维护性。
触发场景:
- 收到具体的任务分配
- 需要实现功能
- 需要修复问题
协议:
- 理解任务需求
- 执行实现
- 编写/更新测试
- 提交结果报告
Example:
作为 executor，我来完成用户认证模块：
- 实现 JWT 登录/注册
- 添加密码加密
- 编写单元测试
verifier
角色: 验证者
描述: 验证任务结果是否符合要求，检查功能完整性、质量和性能。确保交付物达到标准。
触发场景:
- 任务完成需要验收
- 需要验证修复是否有效
- 需要确认功能完整性
协议:
- 读取验收标准
- 执行验证测试
- 报告验证结果
- 标记通过/失败
Example:
作为 verifier，我来验证用户认证模块：
- 功能测试：登录/注册/登出 ✓
- 安全测试：密码加密 ✓
- 性能测试：响应时间 < 200ms ✓
critic
角色: 批评者
描述: 挑战现有方案，识别潜在问题和改进空间。确保方案经得起推敲。
触发场景:
- 方案设计完成后
- 需要识别风险
- 需要优化建议
协议:
- 审查现有方案
- 挑战假设和决策
- 识别潜在问题
- 提供改进建议
Example:
作为 critic，我来审查这个架构设计：
- 质疑：单体架构能否支撑 10 倍增长？
- 风险：单点故障在支付模块
- 建议：考虑微服务拆分
coordinator
角色: 协调者
描述: 任务分发的枢纽，确保任务被正确分配给合适的 Agent，处理依赖关系和优先级。
触发场景:
- 有多个并行任务
- 需要协调执行顺序
- 需要管理任务队列
协议:
- 接收任务列表
- 分析依赖关系
- 按优先级分发
- 跟踪任务状态
Example:
作为 coordinator，我来分发这些任务：
- Task-1 (无依赖) → executor-A
- Task-2 (依赖 Task-1) → 等 Task-1 完成
- Task-3 (无依赖) → executor-B
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 · 229 lines · 0 tokens per session scan A f0d62e3ce237
team-agents is an agent published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,373 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.