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/wshobson/agents/team-debuggit clone --depth 1 https://github.com/wshobson/agentsWhat 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.00011 | $0.00870 |
| Opus 5 | $0.00005 | $0.00435 |
| Sonnet 5 | $0.00002 | $0.00174 |
| Haiku 4.5 | $0.00001 | $0.00087 |
Grade A, and why
team-debug 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Debug
Debug complex issues using the Analysis of Competing Hypotheses (ACH) methodology. Multiple debugger agents investigate different hypotheses in parallel, gathering evidence to confirm or falsify each one.
Pre-flight Checks
- Verify
CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1is set - Parse
$ARGUMENTS:<error-description-or-file>: description of the bug, error message, or path to a file exhibiting the issue--hypotheses N: number of hypotheses to generate (default: 3)--scope: investigation scope —files(specific files),module(module/package),project(entire project)
Phase 1: Initial Triage
- Analyze the error description or file:
- If file path: read the file, look for obvious issues, collect error context
- If error description: search the codebase for related code, error messages, stack traces
- Identify the symptom clearly: what is failing, when, and how
- Gather initial context: recent git changes, related tests, configuration
Phase 2: Hypothesis Generation
Generate N hypotheses about the root cause, covering different failure mode categories:
- Logic Error — Incorrect algorithm, wrong condition, off-by-one, missing edge case
- Data Issue — Invalid input, type mismatch, null/undefined, encoding problem
- State Problem — Race condition, stale cache, incorrect initialization, mutation bug
- Integration Failure — API contract violation, version mismatch, configuration error
- Resource Issue — Memory leak, connection exhaustion, timeout, disk space
- Environment — Missing dependency, wrong version, platform-specific behavior
Present hypotheses to user: "Generated {N} hypotheses. Spawning investigators..."
Phase 3: Investigation
- Use
TeamCreatetool to create the team withteam_name: "debug-{timestamp}"anddescription - For each hypothesis, use
Agenttool to spawn a teammate:name:investigator-{n}(e.g., "investigator-1")subagent_type: "agent-teams:team-debugger"prompt: Include the hypothesis, investigation scope, and relevant context
- Use
TaskCreatefor each investigator's task:- Subject: "Investigate hypothesis: {hypothesis summary}"
- Description: Full hypothesis statement, scope boundaries, evidence criteria
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 · 92 lines · 11 tokens per session scan A 95eadf79ca76
team-debug is a command published in the GitHub repository wshobson/agents (39,318 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 870 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 commands, from other repositories
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
doctor
Diagnose installation health. Check Node, CDP bridge, rn-fast-runner (iOS), rn-android-runner (Android), maestro-runner, simulators, Metro, CDP, injected helpers, ffmpeg, physical devices, plugin version, Vercel rules sync. Reports what's missing — does NOT modify your project.
research_web
Conduct extensive web research on technical topics with validated references.