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/jayminwest/kotadb/do-teamsgit clone --depth 1 https://github.com/jayminwest/kotadbWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/jayminwest/kotadb/do-teams)<a href="https://agentmods.dev/commands/jayminwest/kotadb/do-teams"><img src="https://agentmods.dev/badge/commands/jayminwest/kotadb/do-teams.svg" alt="Measured on agentmods" height="20"></a>What 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.00008 | $0.04120 |
| Opus 5 | $0.00004 | $0.02060 |
| Sonnet 5 | $0.00002 | $0.00824 |
| Haiku 4.5 | $0.00001 | $0.00412 |
Grade A, and why
do-teams 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 5d 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 — 588 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/do-teams - Team Orchestration
Parallel execution using agent teams. You orchestrate the team: spawn teammates, coordinate their work, and synthesize results. All teammates report directly to you.
Your Role
You are the team lead. Your job:
- Create a team
- Spawn ALL teammates directly (flat structure — no intermediate leads)
- Receive their results (automatically delivered)
- Synthesize and report
You do NOT do the work yourself — teammates do. You coordinate.
Official API Constraints
These are hard constraints of the teams system:
| Constraint | Detail |
|---|---|
| No nested teams | Teammates cannot spawn sub-teams or other teammates |
| One team per session | Only one team can be active at a time |
| No session resumption | Cannot resume a session with in-process teammates |
| Lead is fixed | You (the session creator) are lead for the team's lifetime |
| Permissions inherited | All teammates inherit your permission settings at spawn |
| File locking | Task claiming uses file locking to prevent race conditions |
Workflow
Step 1: Create Team
Teammate(
operation: "spawnTeam",
team_name: "{domain}-team",
description: "Working on {requirement summary}"
)
This makes you the team lead. You'll receive messages from teammates automatically.
Step 2: Identify Domain and Load Expertise
Classify the requirement to identify the target domain(s):
| Domain | Keywords | Location |
|---|---|---|
| database | schema, migration, SQLite, FTS5, query, index, table | app/src/db/ |
| api | endpoint, route, MCP tool, HTTP, server, OpenAPI | app/src/api/, app/src/mcp/ |
| testing | test, antimocking, Bun test, SQLite test | app/tests/, tests/ |
| indexer | AST, parser, symbol, reference, code analysis | app/src/indexer/ |
| github | issue, PR, branch, commit, gh CLI | .github/ |
| claude-config | command, hook, settings, .claude | .claude/commands/, .claude/hooks/ |
| agent-authoring | agent, expert domain, tool selection, registry | .claude/agents/ |
| automation | ADW, automated workflow, script, CI/CD | .claude/commands/automation/ |
| documentation | docs, README, API reference, architecture docs | web/docs/content/ |
| web | homepage, blog, CSS, design system, Liquid Glass, kotadb.io, marketing site | web/ |
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.
- 5d ago First seen · 588 lines · 8 tokens per session scan A 0b70a246e300
do-teams is a command published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 4,120 once invoked, about $0.0000 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
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
config
Command "config" from sdebruyn/fabric-dw-mcp-cli, covering configuration & defaults, http retry budget, sql retry budget, mcp workspace allowlist {#mcp-workspace-allowlist} and mcp server log level.
deps-age
Analyze dependency freshness and maintenance activity.
workpm
PM 모드로 오케스트레이터 시작. 팀을 구성하고 5단계 워크플로우로 작업을 완수합니다.