Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Taoidle/plan-cascade/plugin install 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/skills/taoidle/plan-cascade/hybrid-ralph)<a href="https://agentmods.dev/skills/taoidle/plan-cascade/hybrid-ralph"><img src="https://agentmods.dev/badge/skills/taoidle/plan-cascade/hybrid-ralph.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.00052 | $0.03976 |
| Opus 5 | $0.00026 | $0.01988 |
| Sonnet 5 | $0.00010 | $0.00795 |
| Haiku 4.5 | $0.00005 | $0.00398 |
Grade A, and why
hybrid-ralph 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 8d 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 — 553 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hybrid Ralph + Planning-with-Files
A hybrid architecture combining the best of three approaches:
Auto-Recovery Protocol (CRITICAL)
At the START of any interaction, perform this check to recover context after compression/truncation:
-
Check if
.hybrid-execution-context.mdexists in the current directory -
If YES:
- Read the file content using Read tool
- Display: "Detected ongoing hybrid task execution"
- Show current batch and pending stories from the file
- Resume story execution based on the state
- If unsure of state, suggest:
/hybrid:resume --auto
-
If NO but
prd.jsonexists:- Run:
uv run python "${CLAUDE_PLUGIN_ROOT}/skills/hybrid-ralph/scripts/hybrid-context-reminder.py" both - This will generate the context file and display current state
- Run:
This ensures context recovery even after:
-
Context compression (AI summarizes old messages)
-
Context truncation (old messages deleted)
-
New conversation session
-
Claude Code restart
-
Ralph: Structured PRD format (prd.json), progress tracking patterns, small task philosophy
-
Planning-with-Files: 3-file planning pattern (task_plan.md, findings.md, progress.txt), Git Worktree support
-
Claude Code Native: Task tool with subagents for parallel story execution
Quick Start
Automatic PRD Generation
Generate a PRD from your task description:
/hybrid:auto Implement a user authentication system with login, registration, and password reset
This will:
- Launch a Planning Agent to analyze your task
- Generate a PRD with user stories
- Show the PRD for review
- Wait for your approval
Manual PRD Loading
Load an existing PRD file:
/hybrid:manual path/to/prd.json
Approval and Execution
After reviewing the PRD:
/approve
This begins parallel execution of stories according to the dependency graph.
Architecture
File Structure
project-root/
├── prd.json # Product Requirements Document
├── findings.md # Research findings (tagged by story)
├── progress.txt # Progress tracking
├── .current-story # Currently executing story
├── .locks/ # File locks for concurrent access
└── .agent-outputs/ # Individual agent logs
What ships with it
37 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- commands/approve.md 60 KB
- commands/auto.md 26 KB
- commands/complete.md 14 KB
- commands/edit.md 2.9 KB
- commands/manual.md 2.8 KB
- commands/show-dependencies.md 3.6 KB
- commands/status.md 3.6 KB
- commands/worktree.md 32 KB
- core/__init__.py 2.5 KB runs code
- core/agent_executor.py 42 KB runs code
- core/agent_monitor.py 19 KB runs code
- core/cross_platform_detector.py 18 KB runs code
- core/iteration_loop.py 24 KB runs code
- core/orchestrator.py 32 KB runs code
- core/phase_config.py 15 KB runs code
- core/prd_generator.py 16 KB runs code
- core/quality_gate.py 25 KB runs code
- core/retry_manager.py 19 KB runs code
- core/state_manager.py 26 KB runs code
- scripts/agent-exec.py 6.8 KB runs code
- scripts/agent-wrapper.py 20 KB runs code
- scripts/hybrid-context-reminder.py 17 KB runs code
- scripts/hybrid-worktree-complete.ps1 8.7 KB runs code
- scripts/hybrid-worktree-complete.sh 7.5 KB runs code
- scripts/hybrid-worktree-init.ps1 6.5 KB runs code
- scripts/hybrid-worktree-init.sh 5.9 KB runs code
- scripts/memory-doctor.py 8.9 KB runs code
- scripts/prd-generate.py 2.8 KB runs code
- scripts/prd-validate.py 6.8 KB runs code
- scripts/render-plan-docs.py 16 KB runs code
- scripts/show-dependencies.py 8.5 KB runs code
- scripts/status.py 7.7 KB runs code
- scripts/unified-review.py 17 KB runs code
- templates/design_doc.json.example 8.8 KB
- templates/prd_review.md 1.9 KB
- templates/prd.json.example 2.6 KB
- templates/project_design_doc.json.example 8.1 KB
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.
- 8d ago First seen · 553 lines · 52 tokens per session scan A 81658deb61e7
hybrid-ralph is a skill published in the GitHub repository Taoidle/plan-cascade (140 stars, last pushed 5mo ago), licensed MIT. It adds 52 tokens to every session and 3,976 once invoked, about $0.0003 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 skills, from other repositories
dos-goal-fleet
Launch multiple goal-scoped workers in waves, each with a witness-gated stop condition and dos arbitrate file-tree safety. Use when an operator asks to run several independent goals in parallel and fold only verified ships.
dos-dispatch-loop
Run recurring dos-dispatch cycles, switching to dos-replan when the backlog drains and stopping on the kernel's loop verdict. Use for unattended dispatch->replan->dispatch work across disjoint lanes.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-next-up
Snapshot the repo's phased-plan portfolio into a dispatch packet: audit candidates with dos verify, render who-does-what, and emit a dos gate verdict. Use when you need the current next-work view before dispatching agents.
dos-replan
Refresh a plan portfolio from evidence: close shipped queue items, update cooldown state, and surface the few decisions an operator must make. Use after dispatch bursts, drained backlogs, or recurring findings.
dos-class-cycle
Run one DOS plan-class lifecycle tick from the workspace [lifecycle] table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.