Borrowing it
Nothing to install: this file belongs to senda-labs/DQIII8. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/senda-labs/DQIII8/main/.claude/commands/test-team.mdgit clone --depth 1 https://github.com/senda-labs/DQIII8Wrote 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/senda-labs/dqiii8/test-team)<a href="https://agentmods.dev/commands/senda-labs/dqiii8/test-team"><img src="https://agentmods.dev/badge/commands/senda-labs/dqiii8/test-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/senda-labs/dqiii8/test-team"><img src="https://agentmods.dev/badge/commands/senda-labs/dqiii8/test-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.00000 | $0.00151 |
| Opus 5 | $0.00000 | $0.00076 |
| Sonnet 5 | $0.00000 | $0.00030 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
test-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.
What it actually says
/test-team — Agent Team Coordination Test
SSOT:
.claude/skills/test-team/SKILL.md. This command file is a pointer only — read the skill for the two-agent brief, the implementation requirements and thetasks/results/handoff protocol. It previously carried a duplicate copy that held content the skill had dropped: the Kelly implementation requirements (type hints, input-validation bounds, Half-Kelly default, docstring example) and the sequencing contract ("the orchestrator waits for the result from research-analyst before passing context to python-specialist"). Both were merged into the skill on 2026-08-18 (F2).
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 · 11 lines · 0 tokens per session scan A e46c3401692e
test-team is a command published in the GitHub repository senda-labs/DQIII8 (11 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 151 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-30.
Other commands, from other repositories
octo-deliver
Delivery phase - Review, validate, and test with multi-AI quality assurance.
octo-loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
octo-debug
Debug a symptom through reproducible, bounded evidence.
fix-bug
Systematically reproduce, isolate, fix, test, and document a bug.
zeus
A command that runs an automated software-building pipeline from a one-line product description through planning, implementation, review, Docker setup, and testing.
tdd
Test-driven development with observed red and green evidence.