show-dependencies

show-dependencies is a command for coding agents from Taoidle/plan-cascade. It costs 35 tokens per session (911 once invoked), scanned A, original, MIT.

A command that reads a project requirements file (PRD) and maps which stories depend on others. It displays the map as text and examines its critical path, cycles, and bottlenecks.

In plain words
What is it for?
Use it to inspect story order, find circular dependencies, identify bottlenecks, and see which work forms the critical path.
Why use it?
It makes blocked work and dependency problems visible before they delay implementation.

Command

Part of the plan-cascade plugin — 7 skills, 33 commands shipped together

Install

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.

agentmods
npx agentmods add commands/taoidle/plan-cascade/show-dependencies
Clone the repo
git clone --depth 1 https://github.com/Taoidle/plan-cascade

Or install plan-cascade, the plugin that ships this one along with the rest of its 7 skills, 33 commands.

Wrote 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.

agentmods badge for show-dependencies

README.md
[![agentmods](https://agentmods.dev/badge/commands/taoidle/plan-cascade/show-dependencies.svg)](https://agentmods.dev/commands/taoidle/plan-cascade/show-dependencies)
Your own site
<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>
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 911 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash a0c3464a20c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

commands/show-dependencies.md · 154 lines

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.json or in worktree directory
  • Legacy Mode: prd.json in 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"}

============================================================

Read the full file on GitHub · 154 lines

Changes

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.

  1. 3d ago First seen · 154 lines · 35 tokens per session scan A a0c3464a20c1

Subscribe to this mod's changes

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.