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/manualgit 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.00025 | $0.00738 |
| Opus 5 | $0.00013 | $0.00369 |
| Sonnet 5 | $0.00005 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
manual 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.
This is a copy
100% identical to hybrid-manual — 6 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.
How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hybrid Ralph - Load Manual PRD
You are loading an existing Product Requirements Document (PRD) from a file.
Step 1: Parse PRD Path
Get the PRD path from arguments:
PRD_PATH="{{args|first arg or 'prd.json'}}"
Step 2: Verify PRD Exists
if [ ! -f "$PRD_PATH" ]; then
echo "ERROR: PRD file not found: $PRD_PATH"
echo "Please provide a valid path to a prd.json file"
exit 1
fi
Step 3: Read and Validate PRD
Read the PRD file and validate structure:
Required fields:
metadata.descriptiongoalstoriesarray
Each story must have:
idtitledescriptionpriority(high/medium/low)dependencies(array of story IDs)acceptance_criteria(array)
If validation fails, show specific errors and suggest fixes.
Step 4: Copy PRD to Current Directory (if needed)
If the PRD is not already prd.json in the current directory:
if [ "$PRD_PATH" != "prd.json" ]; then
cp "$PRD_PATH" prd.json
echo "Copied PRD to prd.json"
fi
Step 5: Initialize Supporting Files (if missing)
Create findings.md if it doesn't exist:
if [ ! -f "findings.md" ]; then
cat > findings.md << 'EOF'
# Findings
Research and discovery notes will be accumulated here.
Use <!-- @tags: story-id --> to tag sections for specific stories.
EOF
fi
Create progress.txt if it doesn't exist:
if [ ! -f "progress.txt" ]; then
cat > progress.txt << 'EOF'
# Progress Log
Story execution progress will be tracked here.
EOF
fi
Step 6: Display PRD Review
Show a comprehensive PRD review:
============================================================
PRD REVIEW
============================================================
## Goal
{goal from PRD}
## Objectives
- {objective 1}
- {objective 2}
...
## Stories Summary
Total Stories: {count}
By Priority:
High: {count}
Medium: {count}
Low: {count}
## All Stories
### story-001: {title} [High]
Description: {description}
Dependencies: {none or list}
Acceptance Criteria:
- {criterion 1}
- {criterion 2}
...
### story-002: {title} [Medium]
...
## Execution Batches
Batch 1 (parallel):
- story-001
- story-002
Batch 2:
- story-003 (depends on: story-001)
...
============================================================
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 · 154 lines · 25 tokens per session scan A 653a3bbb45ee
manual is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 25 tokens to every session and 738 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to hybrid-manual, differing in 6 lines, and is treated as a copy.
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.