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/show-dependenciesgit 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/show-dependencies)<a href="https://agentmods.dev/commands/taoidle/plan-cascade/show-dependencies"><img src="https://agentmods.dev/badge/commands/taoidle/plan-cascade/show-dependencies.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 | $0.00035 | $0.00911 |
| Opus 5 | $0.00017 | $0.00456 |
| Sonnet 5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
show-dependencies 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 3d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hybrid Ralph - Show Dependencies
You are displaying the dependency graph and analysis for all stories in the PRD.
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
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"
exit 1
fi
Step 2: Read PRD
Read the PRD file at $PRD_PATH to get all stories and their dependencies.
Step 3: Build Dependency Graph
Create a mapping of:
- Story → Dependencies (what this story depends on)
- Story → Dependents (what depends on this story)
- Story → Depth (how many levels from root)
Step 4: Detect Issues
Check for Circular Dependencies
Use depth-first search to detect cycles:
For each story:
Mark as visiting
For each dependency:
If dependency is visiting → CYCLE DETECTED
If dependency not visited → recurse
Mark as visited
Check for Orphan Stories
Find stories with:
- No dependencies
- No dependents
Check for Bottlenecks
Find stories with many dependents (threshold: 4+).
Step 5: Display Dependency Report
============================================================
DEPENDENCY GRAPH
============================================================
## Visual Graph
{ASCII tree showing dependencies}
Example:
story-001 (Database Schema)
│
├─── story-002 (User Registration)
│ │
│ └─── story-004 (Password Reset)
│
└─── story-003 (User Login)
│
└─── story-004 (Password Reset)
## Dependency Details
{For each story, show:
- ID and title
- Dependencies (if any)
- Depth level
- Dependents (if any)
- Type (root, intermediate, endpoint, orphan, bottleneck)
}
## Analysis
- Maximum depth: {depth} levels
- Critical path length: {count} stories
- Bottleneck stories: {list}
- Circular dependencies: {count or "none detected"}
- Orphan stories: {count or "none detected"}
============================================================
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.
- 3d ago First seen · 154 lines · 35 tokens per session scan A a0c3464a20c1
show-dependencies is a command published in the GitHub repository Taoidle/plan-cascade (131 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 911 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
delegate
Delegate a task to any engine and model through the anymodel-runner subagent.
choose
Pick an AnyModel action, provider, and model through an interactive semantic chain.
delegate-with
Delegate through an interactive provider and model selection chain.
review-with
Run an adversarial review through an interactive provider and model selection chain.
setup
Check local engine and provider setup, and optionally toggle the stop-time review gate.
/opsx-ff
Create a change and generate all artifacts needed for implementation in one go.