dep

Issue-dependency commands for linking work items and viewing how they relate. They support blockers, related issues, parent-and-child tasks, and issues discovered during work.

In plain words
What is it for?
Add or remove links between issues, inspect dependency trees, export them as Mermaid flowcharts or JSON, and detect cycles.
Why use it?
They make task order and blockers visible, and can reveal circular dependencies that prevent work from progressing.

Command

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/gastownhall/beads/dep
Clone the repo
git clone --depth 1 https://github.com/gastownhall/beads
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 873 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.00004 $0.00873
Opus 5 $0.00002 $0.00436
Sonnet 5 $0.00001 $0.00175
Haiku 4.5 $0.00000 $0.00087

Measured yesterday against content hash 2d50ea5c65e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dep 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • dep — 100% identical, 2 lines differ
plugins/beads/skills/beads/commands/dep.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Manage dependencies between beads issues.

Available Commands

  • add: Add a dependency between issues

    • $1: "add"
    • $2: From issue ID
    • $3: To issue ID
    • $4: Dependency type (blocks, related, parent-child, discovered-from)
  • remove: Remove a dependency

    • $1: "remove"
    • $2: From issue ID
    • $3: To issue ID
  • tree: Show dependency tree for an issue

    • $1: "tree"
    • $2: Issue ID
    • Flags:
      • --reverse: Show dependent tree (what was discovered from this) instead of dependency tree (what blocks this)
      • --format mermaid: Output as Mermaid.js flowchart (renders in GitHub/GitLab markdown)
      • --json: Output as JSON
      • --max-depth N: Limit tree depth (default: 50)
      • --show-all-paths: Show all paths (no deduplication for diamond dependencies)
  • cycles: Detect dependency cycles

Dependency Types

  • blocks: Hard blocker (from blocks to) - affects ready queue
  • related: Soft relationship - for context only
  • parent-child: Epic/subtask relationship
  • discovered-from: Track issues found during work

Mermaid Format

The --format mermaid option outputs the dependency tree as a Mermaid.js flowchart:

Example:

bd dep tree bd-1 --format mermaid

Output can be embedded in markdown:

```mermaid
flowchart TD
  bd-1["◧ bd-1: Main task"]
  bd-2["☑ bd-2: Subtask"]

  bd-1 --> bd-2
```

Status Indicators:

Each node includes a symbol indicator for quick visual status identification:

  • Open - Not started yet (empty checkbox)
  • In Progress - Currently being worked on (half-filled box)
  • Blocked - Waiting on something (warning sign)
  • Closed - Completed! (checked checkbox)

The diagram colors are determined by your Mermaid theme (default, dark, forest, neutral, or base). Mermaid diagrams render natively in GitHub, GitLab, VSCode markdown preview, and can be imported to Miro.

Examples

  • bd dep add bd-10 bd-20 --type blocks: bd-10 depends on bd-20 (bd-20 blocks bd-10)
  • bd dep tree bd-20: Show what blocks bd-20 (dependency tree going UP)
  • bd dep tree bd-1 --reverse: Show what was discovered from bd-1 (dependent tree going DOWN)
  • bd dep tree bd-1 --reverse --max-depth 3: Show discovery tree with depth limit
  • bd dep tree bd-20 --format mermaid > tree.md: Generate Mermaid diagram for documentation
  • bd dep cycles: Check for circular dependencies

Read the full file on GitHub · 102 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. yesterday First seen · 102 lines · 4 tokens per session scan A 2d50ea5c65e0

Subscribe to this mod's changes

dep is a command published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 873 once invoked, about $0.0000 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.