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/taoidle/plan-cascade/editgit clone --depth 1 https://github.com/Taoidle/plan-cascadeWhat 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 | $0.00038 | $0.00825 |
| Opus 5 | $0.00019 | $0.00413 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
edit 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 2d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hybrid Ralph - Edit PRD
You are opening the PRD file for manual editing.
Path Storage Modes
PRD file location depends on the storage mode:
- New Mode:
~/.plan-cascade/<project-id>/prd.jsonor in worktree directory - Legacy Mode:
prd.jsonin project root or worktree
The command uses PathResolver to find the correct file location.
Step 1: Verify PRD Exists
# Get PRD path from PathResolver
PRD_PATH=$(uv run python -c "from plan_cascade.state.path_resolver import PathResolver; from pathlib import Path; print(PathResolver(Path.cwd()).get_prd_path())" 2>/dev/null || echo "prd.json")
# Also check local prd.json (in worktree)
if [ -f "prd.json" ]; then
PRD_PATH="prd.json"
elif [ ! -f "$PRD_PATH" ]; then
echo "ERROR: No PRD found at: $PRD_PATH"
echo "Please generate one first with:"
echo " /plan-cascade:hybrid-auto <description>"
echo " /plan-cascade:hybrid-manual <path>"
exit 1
fi
Step 2: Open in Editor
Open the PRD file with the system's default editor:
# Detect platform and open editor
if [[ "$OSTYPE" == "msys" || "$OSTYPE" == "win32" || "$OS" == "Windows_NT" ]]; then
# Windows
start "$PRD_PATH"
elif [[ "$OSTYPE" == "darwin"* ]]; then
# macOS
open "$PRD_PATH"
else
# Linux - use $EDITOR or fallback
${EDITOR:-nano} "$PRD_PATH"
fi
Tell the user:
Opening PRD at: {PRD_PATH} in your default editor...
Make your changes, then save and close the editor to continue.
Step 3: Wait for Editor to Close
Wait for the user to finish editing. (The editor command will block until closed.)
Step 4: Validate Updated PRD
After the editor closes, validate the modified PRD:
# Check JSON syntax
if ! uv run python -m json.tool "$PRD_PATH" > /dev/null 2>&1; then
echo "ERROR: Invalid JSON in PRD at: $PRD_PATH"
echo "Please fix the syntax errors and run /plan-cascade:edit again"
exit 1
fi
Validate structure:
- Has
metadata,goal,objectives,stories - Each story has required fields
- Story IDs are unique
- Dependency references exist
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.
- 2d ago First seen · 110 lines · 38 tokens per session scan A b4a79d0b454a
edit is a command published in the GitHub repository Taoidle/plan-cascade (124 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 825 once invoked, about $0.0002 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.
Other commands, from other repositories
conv_release
Command "conv_release" from John-Wendell/Attention-MoA, covering chatbot arena conversations, all conversations and prompt distribution.
data_cleaning
Command "data_cleaning" from John-Wendell/Attention-MoA, covering data cleaning, requirements, steps, convert html to markdown and keep or remove specific languages.
pypi
Command "pypi" from John-Wendell/Attention-MoA, covering requirement and upload.
local_cluster
node-01.
webserver
Command "webserver" from John-Wendell/Attention-MoA, covering install, launch servers, check the launch time, increase the limit of max open files and gradio edit (3.35.2).
leaderboard
Command "leaderboard" from John-Wendell/Attention-MoA, covering get logs, clean battle data, run elo analysis, copy files to hf space and update files on webserver.