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 skills/michael-harris/devteam/devteam-helpnpx skills add michael-harris/devteam --skill 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.00016 | $0.01659 |
| Opus 5 | $0.00008 | $0.00830 |
| Sonnet 5 | $0.00003 | $0.00332 |
| Haiku 4.5 | $0.00002 | $0.00166 |
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 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 — 263 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.
- yesterday First seen · 263 lines · 16 tokens per session scan A 4de15ec18fed
devteam-help is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 1,659 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-30.
Other skills, from other repositories
hydra
Multi-agent orchestration framework for Claude Code. Automatically delegates tasks to cheaper, faster sub-agents (Haiku, Sonnet) while maintaining Opus-level quality through verification. Use when working on any coding task — Hydra activates automatically to route file exploration, test running, documentation, code…
quality-stack
Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when…
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to…
lyra
Transform vague inputs into precision-optimized AI prompts for Claude, ChatGPT, Gemini, or other LLMs. Use when user mentions "optimize prompt", "improve prompt", "lyra", "prompt engineering", or needs help crafting effective AI prompts.
taskfile-setup
Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile…
sops-add-key
Add a new machine's age public key to .sops.yaml and re-encrypt all files. Use for multi-machine setups. Use when user mentions "add key", "add machine", "sops add key", "new machine", "authorize machine", "share key", "add public key", "multi machine sops".