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-listgit 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.00811 |
| Opus 5 | $0.00000 | $0.00405 |
| Sonnet 5 | $0.00000 | $0.00162 |
| Haiku 4.5 | $0.00000 | $0.00081 |
Grade A, and why
devteam-list 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam List Command
Command: /devteam:list
List all development plans and their status.
Usage
/devteam:list # Show all plans
/devteam:list --all # Include archived plans
/devteam:list --type feature # Filter by type
Your Process
Step 1: Read Plan Index
# Load plan index
cat .devteam/plans/index.json
If no index exists:
📋 No plans found.
Create a new plan with:
/devteam:plan "Project description"
Or create a feature plan:
/devteam:plan --feature "Feature description"
Step 2: Display Plan List
╔══════════════════════════════════════════════════════════════╗
║ 📋 DEVELOPMENT PLANS ║
╚══════════════════════════════════════════════════════════════╝
Active: feature-notifications
┌──────────────────────────────────────────────────────────────┐
│ # │ Name │ Type │ Status │ Progress │
├──────────────────────────────────────────────────────────────┤
│ 1 │ Task Manager App │ project │ ✅ complete │ 5/5 │
│ 2 │ Push Notifications │ feature │ 🔄 active │ 1/2 │ ← ACTIVE
│ 3 │ Dark Mode Support │ feature │ 📋 planned │ 0/1 │
└──────────────────────────────────────────────────────────────┘
Commands:
/devteam:select <#> Select a plan to work on
/devteam:implement Execute the active plan
/devteam:plan --feature Create new feature plan
/devteam:archive <#> Archive a completed plan (planned, not yet implemented)
Status Icons
| Icon | Status | Meaning |
|---|---|---|
| 📋 | planned |
Plan created, not started |
| 🔄 | in_progress |
Currently being executed |
| ✅ | complete |
All sprints finished |
| ⏸️ | paused |
Execution paused |
| ❌ | failed |
Circuit breaker triggered |
| 📦 | archived |
Moved to archive |
With --all Flag
Include archived plans:
╔══════════════════════════════════════════════════════════════╗
║ 📋 DEVELOPMENT PLANS (including archived) ║
╚══════════════════════════════════════════════════════════════╝
Active Plans:
│ # │ Name │ Type │ Status │ Progress │
│ 1 │ Task Manager App │ project │ ✅ complete │ 5/5 │
│ 2 │ Push Notifications │ feature │ 🔄 active │ 1/2 │
│ 3 │ Dark Mode Support │ feature │ 📋 planned │ 0/1 │
Archived Plans:
│ 4 │ Old Dashboard │ feature │ 📦 archived │ 2/2 │
│ 5 │ Cancelled Auth │ feature │ 📦 archived │ 0/3 │
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 · 114 lines · 0 tokens per session scan A 8a2fb9254dca
devteam-list 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 811 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).