Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/swarm-planner.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/swarm-planner)<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/swarm-planner"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/swarm-planner/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/regardv/legendaryteam_for_claude/swarm-planner"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/swarm-planner.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.00000 | $0.01193 |
| Opus 5 | $0.00000 | $0.00596 |
| Sonnet 5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00119 |
Grade A, and why
swarm-planner 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 11d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/swarm-planner - Dependency-Aware Planning
Purpose
Generates a structured execution plan with dependency tracking using the Swarms-inspired planning methodology.
Usage
/swarm-planner "task-description"
/swarm-planner "Build user authentication system"
/swarm-planner "Implement e-commerce checkout flow" --detailed
Options
| Option | Description |
|---|---|
| --detailed | Generate comprehensive plan with risk analysis |
| --waves | Output execution waves for parallel processing |
| --json | Output in JSON format for programmatic use |
| --estimate | Include time/effort estimates |
Workflow
When invoked, @Planner executes the following sequence:
1. Task Analysis
Input: "Build user authentication system"
Analysis:
├─ Complexity: HIGH
├─ Components: Database, API, UI, Security
├─ Dependencies: Schema → API → UI
├─ Parallelizable: ~60%
└─ Security-Critical: YES
2. Decomposition
Break into atomic sub-tasks with clear boundaries:
tasks:
- id: T1
name: "Create user schema"
agent: "@DatabaseAgent"
deps: []
confidence: 95%
- id: T2
name: "Implement auth service"
agent: "@SecurityAgent"
deps: [T1]
confidence: 85%
- id: T3
name: "Create API endpoints"
agent: "@APIAgent"
deps: [T1, T2]
confidence: 80%
3. Dependency Graph
Generate DAG for parallel execution:
Wave 1: [T1] → Foundation (no deps)
Wave 2: [T2, T4] → Core services (depend on T1)
Wave 3: [T3, T5, T6] → Implementation (depend on T2)
Wave 4: [T7, T8] → Testing (depend on T3-T6)
4. Confidence Routing
Route tasks based on confidence scores:
AUTO-PROCEED (≥70%): T1, T2, T3, T4, T6, T7, T8
QUEUE (40-69%): T5 (OAuth integration - 55%)
BLOCK (<40%): None
Output
Default Output (plan.md)
# Execution Plan: User Authentication System
## Summary
- Total Tasks: 8
- Execution Waves: 4
- Parallelizable: 65%
- Human Review Required: 1 task (OAuth)
## Dependency Graph
```mermaid
graph TD
T1[User Schema] --> T2[Auth Service]
T1 --> T4[Password Hashing]
T2 --> T3[API Endpoints]
T4 --> T3
T3 --> T5[OAuth Integration]
T3 --> T6[Auth UI]
T5 --> T7[Integration Tests]
T6 --> T7
T3 --> T8[Unit Tests]
Execution Waves
Wave 1: Foundation
| ID | Task | Agent | Confidence |
|---|---|---|---|
| T1 | Create user schema | @DatabaseAgent | 95% |
Wave 2: Core Services
| ID | Task | Agent | Confidence |
|---|---|---|---|
| T2 | Auth service | @SecurityAgent | 85% |
| T4 | Password hashing | @SecurityAgent | 90% |
...
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.
- 11d ago First seen · 190 lines · 0 tokens per session scan A 04b0a16aa9b9
swarm-planner is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,193 tokens. 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
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
plan-workflow
Generate a skill chain plan for a high-level goal by analyzing the skills registry for input/output compatibility.
statusline
Show the governor fleet in your Claude Code statusline. Explicit, opt-in, and chains — it never replaces an existing statusline.
mpm-init
Initialize or update project for Claude Code and MPM.
orquestar
Macro (4 fases) vs micro (8 pasos): el core del DT resume el flujo en 4 fases (Clarificar → Planificar y validar → Ejecutar → Entregar). Este comando es el desglose en 8 pasos; no es un pipeline alternativo. Fuente canónica del par macro/micro: regla 00-orquestador-core (no redefinir el modelo en otros lugares…
init-rules
Auto-generate .claude/rules/ — path-scoped coding conventions from project analysis. Re-run after codebase changes to update rules while preserving manually added conventions.