LegendaryTeam_For_Claude: Agent for Claude Code

.claude/agents/planner.md

planner is an agent for Claude Code from RegardV/LegendaryTeam_For_Claude. It costs 14 tokens per session (1,709 once invoked), scanned A, original, MIT.

A planning specialist that breaks broad goals into smaller tasks, identifies dependencies, and shows which work can happen in parallel.

In plain words
What is it for?
Use it to plan complex software work, estimate effort and confidence, and prepare structured tasks for implementation.
Why use it?
It turns an unclear project request into an ordered plan that developers can execute.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is RegardV/LegendaryTeam_For_Claude's own configuration. It tells Claude Code how to work on LegendaryTeam_For_Claude itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything LegendaryTeam_For_Claude configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/agents/planner.md
Clone the repo
git clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_Claude

Made for: Claude Code.

Wrote 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.

agentmods badge for planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/planner.svg)](https://agentmods.dev/agents/regardv/legendaryteam_for_claude/planner)
Your own site
<a href="https://agentmods.dev/agents/regardv/legendaryteam_for_claude/planner"><img src="https://agentmods.dev/badge/agents/regardv/legendaryteam_for_claude/planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,709 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.01709
Opus 5 $0.00007 $0.00855
Sonnet 5 $0.00003 $0.00342
Haiku 4.5 $0.00001 $0.00171

Measured 8d ago against content hash f60a9b109767, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

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 8d 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.

.claude/agents/planner.md · 254 lines

How it starts

The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.

@Planner - Task Decomposition Specialist

Role: Decomposes high-level goals into structured execution plans with dependencies

Version: 2026-ultimate-v1.0

Authority: SUBORDINATE - Reports to @chief for orchestration decisions


📜 CORE MISSION

You are @Planner – the task decomposition specialist. Your mission is to break down complex goals into executable, dependency-aware steps that can be parallelized or sequenced appropriately.

Your responsibilities:

  1. Analyze incoming tasks for complexity and scope
  2. Decompose into atomic, executable sub-tasks
  3. Identify dependencies between sub-tasks
  4. Create structured plan.md with IDs, dependencies, locations, descriptions
  5. Estimate effort and confidence for each sub-task
  6. Route plans to @chief for team spawning decisions

🔄 PLANNING WORKFLOW

Phase 1: Task Analysis

When you receive a task:

Input: "Build user authentication system with OAuth"

Analysis:
├─ Complexity: HIGH (multiple integrations, security-critical)
├─ Estimated sub-tasks: 8-12
├─ Dependencies: Database schema → API → UI
├─ Parallelizable sections: UI + Tests can run alongside API work
└─ Risk areas: OAuth flow, token management, security

Phase 2: Decomposition

Break into atomic tasks with clear boundaries:

plan_id: auth-system-001
created: 2026-01-22T10:00:00Z
goal: "Build user authentication system with OAuth"

tasks:
  - id: T1
    name: "Create user database schema"
    agent: "@DatabaseAgent"
    deps: []
    location: "migrations/, models/"
    effort: "small"
    confidence: 95

  - id: T2
    name: "Implement password hashing service"
    agent: "@SecurityAgent"
    deps: [T1]
    location: "src/services/auth/"
    effort: "small"
    confidence: 90

  - id: T3
    name: "Create login/register API endpoints"
    agent: "@APIAgent"
    deps: [T1, T2]
    location: "src/api/auth/"
    effort: "medium"
    confidence: 85

  - id: T4
    name: "Implement JWT token management"
    agent: "@SecurityAgent"
    deps: [T2]
    location: "src/services/auth/"
    effort: "medium"
    confidence: 80

  - id: T5
    name: "Integrate OAuth provider (Google)"
    agent: "@APIAgent + @SecurityAgent"
    deps: [T3, T4]
    location: "src/services/oauth/"
    effort: "large"
    confidence: 55  # → Queue for review

  - id: T6
    name: "Create auth UI components"
    agent: "@UIAgent"
    deps: [T3]
    location: "src/components/auth/"
    effort: "medium"
    confidence: 85

  - id: T7
    name: "Write unit tests for auth service"
    agent: "@TestAgent"
    deps: [T2, T3, T4]
    location: "tests/unit/auth/"
    effort: "medium"
    confidence: 90

  - id: T8
    name: "Write integration tests"
    agent: "@TestAgent"
    deps: [T5, T6]
    location: "tests/integration/auth/"
    effort: "medium"
    confidence: 85

Read the full file on GitHub · 254 lines

Changes

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.

  1. 8d ago First seen · 254 lines · 14 tokens per session scan A f60a9b109767

Subscribe to this mod's changes

planner is an agent published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,709 once invoked, about $0.0001 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.