What is bead-dependency-mapper?

A read-only tool for tracing links between open work items in a Beads (bd) Dolt database. It shows which issues block others, where circular dependencies exist, and what work forms the critical path.

Use it to find the open issues blocking the most other issues, detect direct or indirect cycles, and trace blocking chains toward a target issue.

It helps teams see why work is stuck and avoid following dependency loops. It turns a large list of linked issues into a clearer order of work.

bead-dependency-mapper — Agent for Claude Code by jeremylongshore

Install

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.

Claude Code

/plugin marketplace add jeremylongshore/dolt-mcp-vcs-plugin

Claude Code

/plugin install dolt-mcp-vcs

Made for: Claude Code.

Or install dolt-mcp-vcs, the plugin that ships this one along with the rest of its 1 skill, 5 agents, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/jeremylongshore/dolt-mcp-vcs-plugin/bead-dependency-mapper/github.svg)](https://agentmods.dev/agents/jeremylongshore/dolt-mcp-vcs-plugin/bead-dependency-mapper)

Your own site

<a href="https://agentmods.dev/agents/jeremylongshore/dolt-mcp-vcs-plugin/bead-dependency-mapper"><img src="https://agentmods.dev/badge/agents/jeremylongshore/dolt-mcp-vcs-plugin/bead-dependency-mapper/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/jeremylongshore/dolt-mcp-vcs-plugin/bead-dependency-mapper"><img src="https://agentmods.dev/badge/agents/jeremylongshore/dolt-mcp-vcs-plugin/bead-dependency-mapper.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 839 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.00839
Opus 5	$0.00023	$0.00419
Sonnet 5	$0.00009	$0.00168
Haiku 4.5	$0.00005	$0.00084

Measured 9d ago against content hash 56ccfd4f9b1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

bead-dependency-mapper 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 9d 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.

agents/bead-dependency-mapper.md · 50 lines

How it starts

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

You are a bead dependency mapper. You turn the dependencies table into actionable structure: which open issues are bottlenecks, where the cycles are, and what the critical path looks like.

Introspect the live schema — don't assume it. You run in your own context against the live database via the Dolt MCP. Before trusting any table/column name or dependency-type value, confirm it against the live DB (SHOW TABLES, information_schema.columns, SELECT DISTINCT type FROM dependencies). references/dolt-internals.md is only a directory of authoritative sources, not a schema snapshot — the live schema is the authority.

Your SQL access is read-only (blueprint §3). The mcp__dolt-mcp-vcs__query tool is for SELECT/introspection only — never issue a mutation through it. Any write belongs on an agent-owned branch through the gated client (scripts/dolt-mcp-client.py); merge/push/reset/branch-delete are recommend-only, surfaced for a human.

Core Responsibilities

Identify bottlenecks — open issues blocking the most other open issues.
Detect dependency cycles (direct and, where feasible, indirect).
Map the critical path / blocking chains toward a target issue.
Answer ad-hoc dependency questions via SQL.

Process

Find the database. Call mcp__dolt-mcp-vcs__list_databases to confirm the bead database name; set DOLT_DATABASE/DOLT_PORT.
Run the canned analysis. bash ${CLAUDE_PLUGIN_ROOT:-.}/scripts/dep-graph.sh --top 10 returns the bottleneck ranking plus a direct-cycle check.
Ad-hoc / deeper graphs. Call mcp__dolt-mcp-vcs__query directly. The encoding: a blocks dependency row has issue_id = the BLOCKED issue and depends_on_id = the BLOCKER. Restrict to open-on-both-sides (status<>'closed') for actionable bottlenecks. Use recursive CTEs for multi-hop chains where needed.
Interpret. Translate the ranking into "clear this issue first to unblock N others."

Quality Standards

Distinguish blocks (scheduling dependency) from parent-child (epic membership) — only blocks defines the critical path.
Filter to open-on-both-sides for bottlenecks; a closed blocker isn't blocking anything.
Report IDs with titles.

Read the full file on GitHub · 50 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.

9d ago First seen · 50 lines · 46 tokens per session scan A 56ccfd4f9b1c

Subscribe to this mod's changes

bead-dependency-mapper is an agent published in the GitHub repository jeremylongshore/dolt-mcp-vcs-plugin (4 stars, last pushed 14d ago), licensed Apache-2.0. It adds 46 tokens to every session and 839 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-31.

Claude Code Project management beads bottleneck claude-code-plugin dependencies dolt dolthub graph mcp sql

prd-creator

Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.

shinpr/claude-code-workflows · 44 tokens

tasks-agent

Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.

NikiforovAll/claude-code-rules · 18 tokens

senior-dev

Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.

avelikiy/great_cto · 31 tokens

plan-creation-eng-lead

Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.

QBall-Inc/the-bulwark · 48 tokens

mcg

Product management author and coach. Founder and partner of Silicon Valley Product Group (SVPG, 2001). Author of Inspired: How to Create Tech Products Customers Love (2008, 2017), Empowered: Ordinary People, Extraordinary Products (2020), Loved: How to Rethink Marketing for Tech Products (2022 with Lea Hickman), and…

punt-labs/prfaq · 124 tokens

planner

Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.

joanseg/specmanager · 46 tokens