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-test-teams)<a href="https://agentmods.dev/commands/an8079/take-skills/takes-test-teams"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-test-teams/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-test-teams"><img src="https://agentmods.dev/badge/commands/an8079/take-skills/takes-test-teams.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.00027 | $0.00696 |
| Opus 5 | $0.00014 | $0.00348 |
| Sonnet 5 | $0.00005 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
test-teams 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.
What it actually says
/test-teams - 测试团队组建
组建专业的测试团队，采用混合测试模式进行深度测试。
使用方式
/test-teams
或
组建测试团队
开始测试
团队配置
| 角色 | 数量 | 职责 |
|---|---|---|
| 测试工程师 A | 1 | 自动化测试、回归测试 |
| 测试工程师 B | 1 | 探索性测试、边界测试 |
| 测试工程师 C | 1 | AI 生成测试用例、场景测试 |
| 资深程序员 | 1 | 代码审查、架构问题、技术指导 |
工作模式
混合测试模式
-
自动化测试 - 测试工程师 A 负责
- 单元测试覆盖
- 集成测试
- 回归测试套件
-
探索性测试 - 测试工程师 B 负责
- 边界条件测试
- 异常场景测试
- 随机测试
-
AI 生成测试 - 测试工程师 C 负责
- 基于需求生成测试用例
- 使用 /agent-browser 进行 UI 测试
- 生成边界值测试数据
-
代码审查 - 资深程序员负责
- 代码质量审查
- 架构问题识别
- 安全漏洞检测
共识机制
- 测试团队内部所有人达成共识后才算完成
- 不包括用户（用户只负责触发和查看结果）
- 共识达成后输出最终测试报告
使用技能
skills/tdd-workflow/SKILL.md- TDD 工作流skills/webapp-testing/SKILL.md- Web 应用测试/agent-browser- 浏览器自动化测试
输出内容
| 输出 | 说明 |
|---|---|
| 测试计划 | 测试策略、用例、时间安排 |
| 测试执行记录 | 每轮测试的结果 |
| 发现的问题 | Bug 列表、严重程度 |
| 代码审查报告 | 问题列表、改进建议 |
| 最终共识 | 团队一致通过的结论 |
与 /qa 的区别
| 维度 | /test-teams | /qa |
|---|---|---|
| 人员 | 3测试员+1资深 | 单人标准测试 |
| 深度 | 深入探索性测试 | 标准化测试 |
| 共识 | 团队内部共识 | 无需共识 |
| 适用 | 重要功能、复杂场景 | 常规验证 |
提示： /test-teams 会组建团队进行深入测试，直到团队内部达成共识。这需要更多时间，但测试更全面。
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 · 90 lines · 27 tokens per session scan A 50cb9a9501c8
test-teams is a command published in the GitHub repository an8079/take-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 696 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
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.