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.
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWrote 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/gantisstorm/essentials-claude-code/implement-team)<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/implement-team"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/implement-team/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/implement-team"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/implement-team.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00007 | $0.02521 |
| Opus 5.5 | $0.00003 | $0.01008 |
| Sonnet 5.5 | $0.00001 | $0.00504 |
| Haiku 4.5 | $0.00001 | $0.00252 |
Grade C, and why
implement-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 1mo 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Team Command
Execute implementation from conversation context using Agent Teams — full Claude Code instances coordinated through contracts in tmux split panes. All agents complete → done.
Note: Team, swarm, and loop are all execution modes. 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.
Source: Conversation context + argument input + mentioned files.
Uses Claude Code's built-in Task Management System for dependency tracking and visual progress (ctrl+t).
Arguments
<task description>(required): What to implement--agents N(optional): Number of agents (if omitted, determined automatically from scope 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: Analyze Context and Define Scope
ONLY use what's already available:
- The user's argument input
- Conversation history (already in context)
DO NOT:
- Read files unless the user explicitly asks you to
- Grep or explore the codebase
- Use Glob to find files
Understand from context:
- What are we building?
- What are the major components/layers?
- What technologies are involved?
- What are the dependencies between components?
If the conversation context doesn't provide enough information to define integration contracts (exact API shapes, shared types, database schemas), ask the user for clarification before proceeding. You need enough detail to write exact contracts — without them, agents will diverge on interfaces.
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.
- 1mo ago First seen · 261 lines · 7 tokens per session scan C 0f113ecd54c9
implement-team is a command published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 7 tokens to every session and 2,521 once invoked, about $0.0000 per session on Opus 5.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
impact
Which tests a change impacts, with a ready-to-run test command.
map
Generate MAP.md — a relational map of every file, function, signature, and call in the repo.
sanity
Cross-check a dekko callers/uses result against a targeted grep before trusting a low/zero count.
doctor
Diagnose dekko environment/install issues (PATH shadowing, map freshness, MCP registration, plugin, hooks, CLAUDE.md policy block).
search
Search your past agent sessions (Claude Code, Codex, opencode) by keyword.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.