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.
git clone --depth 1 https://github.com/Taoidle/plan-cascadeWrote 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/taoidle/plan-cascade/auto)<a href="https://agentmods.dev/commands/taoidle/plan-cascade/auto"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/auto/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/taoidle/plan-cascade/auto"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/auto.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.00041 | $0.08637 |
| Opus 5.5 | $0.00016 | $0.03455 |
| Sonnet 5.5 | $0.00008 | $0.01727 |
| Haiku 4.5 | $0.00004 | $0.00864 |
Grade A, and why
auto 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.
How it starts
The opening of the file, as written. The whole thing — 939 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Cascade - Auto Strategy Executor
AI automatically analyzes the task and executes the optimal strategy without user confirmation.
CRITICAL CONSTRAINTS (READ FIRST)
NEVER use EnterPlanMode. This command has its own planning and execution flow. Using Claude's native plan mode bypasses Plan Cascade entirely and defeats the purpose of this command. If you feel the urge to "enter plan mode" or "design an implementation approach", STOP — that is exactly what the Skill tool routing in Step 5 handles.
NEVER use the Task tool with subagent_type=Explore or subagent_type=Plan during this command's execution. Context gathering in Step 2 must use only Glob, Read, Grep, and Bash (for git commands only). Launching exploration agents delays routing and causes fallthrough to native plan mode.
After completing Step 3 (strategy analysis), you MUST proceed directly to Step 5 (Skill tool routing). Do not pause to "think about the approach", "gather more context", or "design a solution". The specialized skill invoked in Step 5 handles all of that.
Command-Line Flags
The auto command supports the following flags to customize execution:
Parameter Priority
When parameters are specified in multiple places, the following priority order applies:
- Command-line flags (highest priority) - Override all other sources
- Configuration files (prd.json, mega-plan.json) - Used when no command-line flag provided
- Default values (lowest priority) - Used when no other source provides the parameter
Example:
# If prd.json contains: flow_config.level = "standard"
# And you run: /plan-cascade:auto --flow full "task"
# Result: FLOW = "full" (command-line overrides configuration)
Note: Parameters are propagated through the execution chain:
auto→ passes parameters tohybrid-auto/hybrid-worktree/mega-plan- These commands → save parameters to
prd.json/mega-plan.json approve→ reads parameters from configuration files (can be overridden by command-line)
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.
- 1mo ago First seen · 939 lines · 41 tokens per session scan A 05f9a46c9d0d
auto is a command published in the GitHub repository Taoidle/plan-cascade (133 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 8,637 once invoked, about $0.0002 per session on Opus 5.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.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
create-epo-patent
Create a complete EPO-compliant patent application from invention disclosure through filing-ready package.
search-flights
Search award flight availability across airlines.
guide
Interactive guide to fellowship. Walks you through a real task using the structured research-plan-implement flow, then shows you what's next.
ui-audit
Run comprehensive UI/UX design validation against design principles, accessibility standards, and usability laws.
board-review
Quick board review - get expert opinions from 5 directors without full deliberation.