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 commands/michael-harris/devteam/devteam-testgit clone --depth 1 https://github.com/michael-harris/devteamWhat 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 | $0.00000 | $0.00624 |
| Opus 5 | $0.00000 | $0.00312 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00062 |
Grade A, and why
devteam-test 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 yesterday.
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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam Test Command
Command: /devteam:test [target] [options]
Coordinate test writing and execution across the project. Launches the Test Coordinator to orchestrate language-specific test writers and verification agents.
Usage
# Write tests for current task
/devteam:test
# Write tests for specific files
/devteam:test "src/api/auth.ts"
# Write specific test types
/devteam:test --type unit
/devteam:test --type integration
/devteam:test --type e2e
# Write tests for a scope
/devteam:test --scope "src/services/"
# Run existing tests and fill coverage gaps
/devteam:test --coverage
/devteam:test --coverage --threshold 80
# Cost-optimized
/devteam:test --eco
Options
| Option | Description |
|---|---|
--type <type> |
Test type: unit, integration, e2e, all |
--scope <path> |
Limit to specific files/directories |
--coverage |
Analyze coverage and fill gaps |
--threshold <pct> |
Coverage threshold percentage (default: 80) |
--eco |
Cost-optimized execution |
Your Process
Phase 0: Initialize Session
source scripts/state.sh
source scripts/events.sh
SESSION_ID=$(start_session "/devteam:test $*" "test")
log_session_started "/devteam:test $*" "test"
Phase 1: Launch Test Coordinator
Delegate to the quality:test-coordinator agent, which will:
- Analyze target code to determine test needs
- Select appropriate test writers based on language
- Coordinate unit, integration, and e2e test writing
- Run tests and verify they pass
- Report coverage metrics
const result = await Task({
subagent_type: "quality:test-coordinator",
prompt: `Test coordination request:
Target: ${target || 'current task files'}
Type: ${type || 'all'}
Scope: ${scope || 'auto-detect'}
Coverage mode: ${coverageMode}
Threshold: ${threshold || 80}
Coordinate test writers to produce:
1. Unit tests for individual functions/methods
2. Integration tests for component interactions
3. E2E tests for critical user flows
4. Edge case and error handling tests
5. Coverage report and gap analysis`
})
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.
- yesterday First seen · 103 lines · 0 tokens per session scan A 412b11e56d55
devteam-test is a command published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 624 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
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
map
View, rebuild, or query the codebase dependency map.
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
code-explain
Explain complex code through clear narratives and visual diagrams.
health
Run documentation health checks (freshness, links, drift, cross-doc consistency).