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-helpgit 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.01884 |
| Opus 5 | $0.00000 | $0.00942 |
| Sonnet 5 | $0.00000 | $0.00377 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
devteam-help 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 2d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevTeam Help Command
Command: /devteam:help [topic]
Get help on DevTeam commands, concepts, and troubleshooting.
Usage
/devteam:help # Show command overview
/devteam:help implement # Help for specific command
/devteam:help eco # Help on eco mode
/devteam:help agents # Help on agent system
/devteam:help troubleshooting # Troubleshooting guide
Available Topics
Commands
| Topic | Description |
|---|---|
plan |
Planning and PRD generation |
implement |
Implementation execution |
bug |
Bug fixing workflow |
issue |
GitHub issue handling |
status |
System status and metrics |
reset |
Reset and recovery |
config |
Configuration management |
logs |
Log viewing |
Concepts
| Topic | Description |
|---|---|
eco |
Eco mode for cost optimization |
task-loop |
Task Loop quality loop |
interview |
Interview system |
research |
Research phase |
escalation |
Model escalation |
gates |
Quality gates |
council |
Bug Council |
agents |
Agent system |
worktrees |
Git worktree automation |
Guides
| Topic | Description |
|---|---|
getting-started |
New user guide |
troubleshooting |
Problem solving |
best-practices |
Recommended practices |
migration |
Migrating from v2.x |
Your Process
Step 1: Resolve Topic
function resolveTopic(input) {
// Exact match
if (topics[input]) return topics[input]
// Command alias
if (commandAliases[input]) return topics[commandAliases[input]]
// Fuzzy match
const matches = findSimilar(input, Object.keys(topics))
if (matches.length) {
return { type: 'suggestion', matches }
}
return { type: 'not_found' }
}
Step 2: Display Help
No Topic (Overview):
╔═══════════════════════════════════════════════════════════════╗
║ DevTeam v3.4 Help ║
╚═══════════════════════════════════════════════════════════════╝
Quick Start
───────────────────────────────────────────────────────────────
/devteam:plan Create a project plan
/devteam:implement Execute implementation
/devteam:bug "issue" Fix a bug
/devteam:status Check system status
Common Commands
───────────────────────────────────────────────────────────────
Plan & Execute
/devteam:plan Interactive planning with research
/devteam:implement Execute plans, sprints, or tasks
/devteam:implement --eco Cost-optimized execution
Bug Fixing
/devteam:bug Fix local bugs
/devteam:issue #123 Fix GitHub issues
Management
/devteam:status System health and costs
/devteam:list List plans and tasks
/devteam:reset Reset stuck sessions
Get Help on Specific Topics
───────────────────────────────────────────────────────────────
/devteam:help <command> Help for a command
/devteam:help eco Eco mode explanation
/devteam:help task-loop Quality loop details
/devteam:help troubleshooting Problem solving
Documentation: https://github.com/michael-harris/devteam
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.
- 2d ago First seen · 277 lines · 0 tokens per session scan A 345054f447db
devteam-help 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 1,884 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).