agentmods.dev

plan-to-beads

A command that turns a Claude Code plan file into a Beads epic and its tasks. An epic is a larger piece of work made up of smaller tasks, with dependencies showing their order.

In plain words
What is it for?
Use it to find a plan file, create its epic and phase tasks, connect the tasks in order, and link them to the epic.
Why use it?
It avoids copying a written plan into the issue tracker by hand. The resulting tasks can be followed across sessions and their required sequence is recorded.

Command

27k +29 yesterday A scan 0 tokens original MIT
View the source file gastownhall/beads
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/plan-to-beads
Clone the repo
git clone --depth 1 https://github.com/gastownhall/beads
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 470 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.00000 $0.00470
Opus 5 $0.00000 $0.00235
Sonnet 5 $0.00000 $0.00094
Haiku 4.5 $0.00000 $0.00047

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

Security

Grade A, and why

plan-to-beads 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.

integrations/claude-code/commands/plan-to-beads.md · 63 lines

What it actually says

Convert Plan to Beads Tasks

description:

Convert a Claude Code plan file into beads epic + tasks for cross-session tracking.

Arguments

$ARGUMENTS (optional - path to plan file, defaults to most recent in ~/.claude/plans/)

Use the Task tool with subagent_type='general-purpose' to convert the plan.

Agent Instructions

The agent should:

  1. Find the plan file

    • If argument provided, use that path
    • Otherwise: ls -t ~/.claude/plans/*.md | head -1

  2. Parse the plan structure

    • Title: First # Plan: or # heading
    • Description: Content under ## Summary
    • Tasks: Each ### Phase N: or ### N. section
    • File list: Include in epic description

  3. Create the epic

    bd create "[Plan Title]" -t epic -p 1 -d "[summary]. Files: N to modify." --json

  4. Create tasks from phases

    • Each phase becomes a task
    • Use first paragraph of phase content as description
    bd create "[Phase title]" -t task -p 2 -d "[description]" --json

  5. Add sequential dependencies

    • Phases are sequential: bd dep add <phase2> <phase1>

  6. Link tasks to epic

    • bd dep add <epic> <task> for each task

  7. Return a concise summary (not raw output):

    Created from: [filename]

Epic: [title] ([epic-id])
  ├── [Phase 1] ([id]) - ready
  ├── [Phase 2] ([id]) - blocked by [prev]
  └── [Phase 3] ([id]) - blocked by [prev]

Total: [N] tasks
Run `bd ready` to start.

Notes

  • Original plan file is preserved for reference
  • Task descriptions use first paragraph only (keeps them scannable)
  • Sequential phases get automatic dependencies
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 · 63 lines · 0 tokens per session scan A 55c2a31f46b5

Subscribe to this mod's changes

plan-to-beads is a command published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 470 tokens. 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.

Planningagentsclaude-codecoding
Related

Other commands, from other repositories

update-changelog-and-tag

You are preparing a release. Follow these steps precisely.

sandst1/remind · 0 tokens

lavra-work-teams

Work on multiple beads with persistent worker teammates that self-organize through a ready queue.

roberto-mello/lavra · 22 tokens

lavra-retro

Weekly retrospective with shipping analytics, team performance, and knowledge synthesis.

roberto-mello/lavra · 17 tokens

lavra-work-ralph

Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.

roberto-mello/lavra · 27 tokens

lavra-qa

Browser-based QA verification of the running app -- systematic testing from the user's perspective.

roberto-mello/lavra · 20 tokens

lavra-ship

Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.

roberto-mello/lavra · 21 tokens