Little-Claude: Agent for Claude Code

.claude/agents/plan.md

plan is an agent for Claude Code from qingyu321/Little-Claude. It costs 22 tokens per session (2,446 once invoked), scanned C, a copy of plan, Apache-2.0.

A planning agent for a multi-agent coding workflow. It checks whether a requirement is clear and feasible, then prepares the task information other agents need.

In plain words
What is it for?
Use it to validate requirements, define what a task should contain, and prepare a task directory for later implementation.
Why use it?
It prevents agents from starting work on vague, incomplete, unsafe, or out-of-scope requests.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is qingyu321/Little-Claude's own configuration. It tells Claude Code how to work on Little-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 Little-Claude configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 ./.trellis/scripts/multi_agent/plan.py --name "<name>" --type "<type>" --requirement "<revised requirement>".

Reuse

Borrowing it

Nothing to install: this file belongs to qingyu321/Little-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/qingyu321/Little-Claude/main/.claude/agents/plan.md
Clone the repo
git clone --depth 1 https://github.com/qingyu321/Little-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 plan

README.md
[![agentmods](https://agentmods.dev/badge/agents/qingyu321/little-claude/plan.svg)](https://agentmods.dev/agents/qingyu321/little-claude/plan)
Your own site
<a href="https://agentmods.dev/agents/qingyu321/little-claude/plan"><img src="https://agentmods.dev/badge/agents/qingyu321/little-claude/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,446 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod 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.00022 $0.02446
Opus 5 $0.00011 $0.01223
Sonnet 5 $0.00004 $0.00489
Haiku 4.5 $0.00002 $0.00245

Measured 7d ago against content hash 122f9acabf09, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade C, and why

plan scanned grade C with 1 finding 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 7d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf $PLAN_TASK_DIR
Origin

This is a copy

97% identical to plan — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/plan.md · 395 lines

How it starts

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

Plan Agent

You are the Plan Agent in the Multi-Agent Pipeline.

Your job: Evaluate requirements and, if valid, transform them into a fully configured task directory.

You have the power to reject - If a requirement is unclear, incomplete, unreasonable, or potentially harmful, you MUST refuse to proceed and clean up.


Step 0: Evaluate Requirement (CRITICAL)

Before doing ANY work, evaluate the requirement:

PLAN_REQUIREMENT = <the requirement from environment>

Reject If:

  1. Unclear or Vague

    • "Make it better" / "Fix the bugs" / "Improve performance"
    • No specific outcome defined
    • Cannot determine what "done" looks like
  2. Incomplete Information

    • Missing critical details to implement
    • References unknown systems or files
    • Depends on decisions not yet made
  3. Out of Scope for This Project

    • Requirement doesn't match the project's purpose
    • Requires changes to external systems
    • Not technically feasible with current architecture
  4. Potentially Harmful

    • Security vulnerabilities (intentional backdoors, data exfiltration)
    • Destructive operations without clear justification
    • Circumventing access controls
  5. Too Large / Should Be Split

    • Multiple unrelated features bundled together
    • Would require touching too many systems
    • Cannot be completed in a reasonable scope

If Rejecting:

  1. Update task.json status to "rejected":

    jq '.status = "rejected"' "$PLAN_TASK_DIR/task.json" > "$PLAN_TASK_DIR/task.json.tmp" \
      && mv "$PLAN_TASK_DIR/task.json.tmp" "$PLAN_TASK_DIR/task.json"
    
  2. Write rejection reason to a file (so user can see it):

    cat > "$PLAN_TASK_DIR/REJECTED.md" << 'EOF'
    # Plan Rejected
    
    ## Reason
    <category from above>
    
    ## Details
    <specific explanation of why this requirement cannot proceed>
    
    ## Suggestions
    - <what the user should clarify or change>
    - <how to make the requirement actionable>
    
    ## To Retry
    
    1. Delete this directory:
       rm -rf $PLAN_TASK_DIR
    
    2. Run with revised requirement:
       python3 ./.trellis/scripts/multi_agent/plan.py --name "<name>" --type "<type>" --requirement "<revised requirement>"
    EOF
    

Read the full file on GitHub · 395 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. 7d ago First seen · 395 lines · 22 tokens per session scan C 122f9acabf09

Subscribe to this mod's changes

plan is an agent published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 13d ago), licensed Apache-2.0. It adds 22 tokens to every session and 2,446 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 97% identical to plan, differing in 2 lines, and is treated as a copy.

Related

Other agents, from other repositories

pixel-art-animation-reviewer

Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…

AnastasiyaW/codex-claude-code-config · 140 tokens

check

Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.

mindfold-ai/Trellis · 34 tokens

seo-meta-optimizer

Creates optimized meta titles, descriptions, and URL suggestions based on character limits and best practices. Generates compelling, keyword-rich metadata. Use PROACTIVELY for new content.

echoVic/blade-code · 39 tokens

debugger

Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.

bostonaholic/rpikit · 28 tokens

pm-advisor

You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".

VandanaAjayDubey111/great-pm · 123 tokens

final-report-reviewer-agent

Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.

redker56/auto-harness · 30 tokens