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/gantisstorm/essentials-claude-code/plan-teamgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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.00013 | $0.02538 |
| Opus 5 | $0.00006 | $0.01269 |
| Sonnet 5 | $0.00003 | $0.00508 |
| Haiku 4.5 | $0.00001 | $0.00254 |
Grade C, and why
plan-team scanned grade C with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
1. **tmux installed**: Run `which tmux` — if not found, tell the user to install it (`brew install tmux` on macOS, `sudo apt install tmux` on Linux) and exit Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **Agent Teams enabled**: Run `echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` — if not `1`, tell the user to enable it in `~/.claude/settings.json` under `"env": {"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"}` or export it Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- "Backend: what exact curl commands test each endpoint?" How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Team Command
Execute a plan file using Agent Teams — full Claude Code instances coordinated through contracts in tmux split panes. Requires a plan file. All agents complete → done.
Note: Team, swarm, and loop are all execution modes for plans. Use teams when components need to integrate and agents need to agree on interfaces (frontend + backend + database). Use swarms for independent parallel tasks. Use loops for sequential work.
Uses Claude Code's built-in Task Management System for dependency tracking and visual progress (ctrl+t).
Supported Plan Types
This command works with plans from:
/plan-creator- Implementation plans/bug-plan-creator- Bug fix plans/code-quality-plan-creator- LSP-powered quality plans
Arguments
<plan_path>(required): Path to the plan file--agents N(optional): Number of agents (if omitted, determined automatically from plan complexity)
Instructions
Step 1: Check Prerequisites
Verify before proceeding:
- tmux installed: Run
which tmux— if not found, tell the user to install it (brew install tmuxon macOS,sudo apt install tmuxon Linux) and exit - Agent Teams enabled: Run
echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS— if not1, tell the user to enable it in~/.claude/settings.jsonunder"env": {"CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS": "1"}or export it in their shell profile, and exit
Step 2: Read the Plan
Read the plan document. Understand:
- What are we building?
- What are the major components/layers?
- What technologies are involved?
- What are the dependencies between components?
- What are the acceptance/exit criteria?
DO NOT read other files, grep, or explore the codebase — just parse the plan.
Step 3: Determine Team Structure
If --agents N is specified, use that number. Otherwise, analyze the plan and determine optimal team size:
- 2 agents: Simple projects with clear frontend/backend split
- 3 agents: Full-stack apps (frontend, backend, database/infra)
- 4 agents: Complex systems with additional concerns (testing, DevOps, docs)
- 5+ agents: Large systems with many independent modules
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 · 251 lines · 13 tokens per session scan C 8b4ef8cd7b22
plan-team is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 13 tokens to every session and 2,538 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 3 findings (asks for root, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
polyphony-init
Initialize the Polyphony multi-agent orchestration environment.
skill-create
Generate skills from git history analysis.
instinct-import
Import instincts from external sources.
evolve
Analyze instincts and suggest or generate evolved structures.
model-config
View or change the primary model that handles your coding work across srooter (the gateway), the route-task hooks, and Maggy. One setting, read everywhere. Stored in /.claude/model-config.json.
add-agent
Add a new sub-agent to the current plugin for specialized tasks.