Conductor-Beads: Command for Claude Code

.claude/skills/beads/commands/dep.md

dep is a command for Claude Code from NguyenSiTrung/Conductor-Beads. It costs 0 tokens per session (873 once invoked), scanned A, a copy of dep, Apache-2.0.

A command for managing dependencies between Beads issues, where an issue is a tracked piece of work and a dependency records how two issues are related or blocked.

In plain words
What is it for?
Use it to add or remove links between issues, view dependency trees, detect cycles, and export trees as JSON or Mermaid diagrams.
Why use it?
It makes work ordering and blockers visible instead of leaving relationships hidden in issue descriptions or memory.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: positional $N argument.

This is NguyenSiTrung/Conductor-Beads's own configuration. It tells Claude Code how to work on Conductor-Beads itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Conductor-Beads configures →

Reuse

Borrowing it

Nothing to install: this file belongs to NguyenSiTrung/Conductor-Beads. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NguyenSiTrung/Conductor-Beads/main/.claude/skills/beads/commands/dep.md
Clone the repo
git clone --depth 1 https://github.com/NguyenSiTrung/Conductor-Beads

Made for: Claude Code.

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 dep

README.md
[![agentmods](https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/dep/github.svg)](https://agentmods.dev/commands/nguyensitrung/conductor-beads/dep)
Your own site
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/dep"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/dep/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for dep

Your own site · 80×15
<a href="https://agentmods.dev/commands/nguyensitrung/conductor-beads/dep"><img src="https://agentmods.dev/badge/commands/nguyensitrung/conductor-beads/dep.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 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. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00000 $0.00873
Opus 5 $0.00000 $0.00436
Sonnet 5 $0.00000 $0.00175
Haiku 4.5 $0.00000 $0.00087

Measured 10d ago against content hash 2679ab80bfad, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

Origin

This is a copy

100% identical to dep — 2 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.

.claude/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. 10d ago First seen · 102 lines · 0 tokens per session scan A 2679ab80bfad

Subscribe to this mod's changes

dep is a command published in the GitHub repository NguyenSiTrung/Conductor-Beads (24 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 873 tokens. A static security scan graded it A with 0 findings. It is 100% identical to dep, differing in 2 lines, and is treated as a copy.