Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/thewaywithin/agent-11/plangit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/plan)<a href="https://agentmods.dev/commands/thewaywithin/agent-11/plan"><img src="https://agentmods.dev/badge/commands/thewaywithin/agent-11/plan.svg" alt="Measured on agentmods" 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.07472 |
| Opus 5 | $0.00000 | $0.03736 |
| Sonnet 5 | $0.00000 | $0.01494 |
| Haiku 4.5 | $0.00000 | $0.00747 |
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 today.
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 — 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, blockersnext- Show what's coming upphase [N]- Show details for specific phasegate [N]- Show quality gate status for phaseupdate [field] [value]- Update plan fieldarchive- Archive completed phases to reduce context
Command Implementation
Prerequisites
Before executing any /plan command:
- Verify
project-plan.mdexists (created by/bootstrap) - Validate plan structure against
project/schemas/project-plan.schema.yaml - Check for
.context/phase-N-context.yamlfiles for active phases
Error Handling
Common Errors:
- No project-plan.md: "No project plan found. Run
/bootstrapto 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
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.
- today First seen · 1,177 lines · 0 tokens per session scan A a737db8dad8d
plan is a command published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 13d 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.
Other commands, from other repositories
ensemble:generate-project-router-rules
Generate project-specific router rules by analyzing the project's tech stack.
ensemble:generate-router-rules
Generate router rules by introspecting installed agents and skills.
brainstorm
Facilitate a structured brainstorming session for feature development using Scrum Master techniques.
generate-prp
Generate comprehensive PRP (Product Requirements & Plans) with thorough research and validation.
execute-task
Execute individual development tasks from task breakdown documents.
execute-prp
Implement features from PRP specifications with comprehensive validation and testing.