agent-11: Command for Claude Code

.claude/commands/plan.md

plan is a command for Claude Code from TheWayWithin/agent-11. It costs 0 tokens per session (7,472 once invoked), scanned A, original, MIT.

A project-state command for viewing and updating a structured project plan, including phases, progress, blockers, and quality gates.

In plain words
What is it for?
Use it to view status, upcoming work, phase details, gate results, plan fields, or archived phases.
Why use it?
It gives a shared place to see what is happening now, what comes next, and whether each phase has met its checks.

Command for Claude Code

Written for Claude Code: installed under .claude/.

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

Reuse

Borrowing it

Nothing to install: this file belongs to TheWayWithin/agent-11. 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/TheWayWithin/agent-11/main/.claude/commands/plan.md
Clone the repo
git clone --depth 1 https://github.com/TheWayWithin/agent-11

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/commands/thewaywithin/agent-11/plan/github.svg)](https://agentmods.dev/commands/thewaywithin/agent-11/plan)
Your own site
<a href="https://agentmods.dev/commands/thewaywithin/agent-11/plan"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/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.

agentmods 80×15 button for plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/thewaywithin/agent-11/plan"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,472 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.00000 $0.07472
Opus 5.5 $0.00000 $0.02989
Sonnet 5.5 $0.00000 $0.01494
Haiku 4.5 $0.00000 $0.00747

Measured 1mo ago against content hash a737db8dad8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

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/commands/plan.md · 1,177 lines

How it starts

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

/plan - Project State Management

Purpose: Primary interface for viewing and managing project state. Provides real-time insights into progress, quality gates, and next actions.

Usage: /plan [subcommand] [args]

Available Subcommands:

  • status - Show current phase, task, progress, blockers
  • next - Show what's coming up
  • phase [N] - Show details for specific phase
  • gate [N] - Show quality gate status for phase
  • update [field] [value] - Update plan field
  • archive - Archive completed phases to reduce context

Command Implementation

Prerequisites

Before executing any /plan command:

  1. Verify project-plan.md exists (created by /bootstrap)
  2. Validate plan structure against project/schemas/project-plan.schema.yaml
  3. Check for .context/phase-N-context.yaml files for active phases

Error Handling

Common Errors:

  • No project-plan.md: "No project plan found. Run /bootstrap to generate one."
  • Invalid schema: "Project plan validation failed. Check against schema at project/schemas/project-plan.schema.yaml"
  • Phase not found: "Phase N not found. Available phases: 1-{total}"
  • Invalid field: "Field '{field}' not recognized. Valid fields: task_status, blockers, current_focus"

Subcommand: /plan status

Purpose: Display current project state at a glance.

Algorithm:

1. Read project-plan.md YAML frontmatter
2. Parse metadata:
   - project_name
   - total_phases
   - current_phase
   - current_task (from current phase)
3. Calculate progress metrics:
   - overall_progress = completed_tasks / total_tasks
   - phase_progress = completed_tasks_current_phase / total_tasks_current_phase
4. Read .context/phase-{current_phase}-context.yaml for:
   - blockers
   - next_action
   - quality_gate_status
5. Format and display output

Output Format:

📊 Project: {project_name}
📍 Phase: {current_phase}/{total_phases} - {phase_name}
📋 Task: {current_task}/{total_tasks_phase} - {task_description}
🎯 Progress: {overall_progress}% overall, {phase_progress}% current phase

⚠️ Blockers: {blockers_list or "None"}
➡️ Next Action: {next_action}

🚦 Quality Gates:
- Phase 1: {status_emoji} {STATUS} ({passed}/{total})
- Phase 2: {status_emoji} {STATUS} ({passed}/{total})
...

Status Legend:
✅ PASSED - All gates passed
🟡 IN PROGRESS - Some gates pending
❌ FAILED - One or more gates failed
⏸️ NOT STARTED - Phase not yet begun

Read the full file on GitHub · 1,177 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. 1mo ago First seen · 1,177 lines · 0 tokens per session scan A a737db8dad8d

Subscribe to this mod's changes

plan is a command published in the GitHub repository TheWayWithin/agent-11 (17 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 7,472 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-09-04.