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/plan.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/plan)<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/plan"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/plan/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/plan"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/plan.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.03730 |
| Opus 5 | $0.00000 | $0.01865 |
| Sonnet 5 | $0.00000 | $0.00746 |
| Haiku 4.5 | $0.00000 | $0.00373 |
Grade A, and why
plan 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 9d 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 — 654 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/plan - Implementation Planning & Strategy
Create detailed implementation plans before coding, ensuring clear strategy and preventing over-engineering.
Usage
# Create implementation plan for a feature
/plan "Add user authentication with OAuth2"
# Plan with specific requirements
/plan "Build shopping cart" --requirements "must support multiple currencies, inventory tracking"
# Plan refactoring
/plan refactor "migrate from Redux to Zustand"
# Plan architecture change
/plan architecture "add microservices for payment processing"
# Generate step-by-step plan
/plan "implement real-time notifications" --detailed
What This Command Does
- Analyzes the requested feature or change
- Breaks down into concrete, actionable steps
- Identifies dependencies and blockers
- Estimates effort and complexity
- Suggests architecture and approach
- Creates task checklist
- Highlights risks and trade-offs
Command Flow
Step 1: Understand requirement
→ Parse user request
→ Identify scope and goals
→ Clarify any ambiguities
Step 2: Analyze current state
→ Review existing code
→ Identify what exists
→ Find integration points
Step 3: Design approach
→ Choose architecture pattern
→ Select technologies
→ Define data models
Step 4: Break into tasks
→ Create step-by-step plan
→ Identify dependencies
→ Estimate complexity
Step 5: Highlight considerations
→ Security implications
→ Performance impacts
→ Testing requirements
→ Deployment needs
Step 6: Create actionable output
→ Task checklist
→ File locations
→ Code structure
Invokes Agent
@ArchitectureAgent will handle this command with the following context:
Task: Create implementation plan
Feature: ${user_input}
Requirements: ${requirements}
Deliverables:
1. High-level approach and architecture
2. Step-by-step implementation plan
3. File structure and organization
4. Dependencies and integration points
5. Testing strategy
6. Security considerations
7. Performance implications
8. Deployment requirements
9. Estimated effort
10. Risk assessment
Output Format:
- Executive summary
- Detailed step-by-step plan
- Task checklist
- Code structure
- Trade-offs and decisions
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.
- 9d ago First seen · 654 lines · 0 tokens per session scan A 937542b9adf9
plan 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 3,730 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.