gastownhall/beads is a command-line graph issue tracker that gives coding agents persistent, structured memory through a dependency-aware task database. It is for developers and AI agents handling long-running work across tasks, branches, and sessions. The catalogue entries provide integrations and workflows for operating Beads with coding agents.
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.
git clone --depth 1 https://github.com/gastownhall/beadsWrote 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.
[](https://agentmods.dev/commands/gastownhall/beads/plan-to-beads)<a href="https://agentmods.dev/commands/gastownhall/beads/plan-to-beads"><img src="https://agentmods.dev/badge/commands/gastownhall/beads/plan-to-beads/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.
<a href="https://agentmods.dev/commands/gastownhall/beads/plan-to-beads"><img src="https://agentmods.dev/badge/commands/gastownhall/beads/plan-to-beads.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.00470 |
| Opus 5.5 | $0.00000 | $0.00188 |
| Sonnet 5.5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
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 1mo 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.
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:
-
Find the plan file
- If argument provided, use that path
- Otherwise:
ls -t ~/.claude/plans/*.md | head -1
-
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
- Title: First
-
Create the epic
bd create "[Plan Title]" -t epic -p 1 -d "[summary]. Files: N to modify." --json -
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 -
Add sequential dependencies
- Phases are sequential:
bd dep add <phase2> <phase1>
- Phases are sequential:
-
Link tasks to epic
bd dep add <epic> <task>for each task
-
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
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.
- 1mo ago First seen · 63 lines · 0 tokens per session scan A 55c2a31f46b5
plan-to-beads is a command published in the GitHub repository gastownhall/beads (27,917 stars, last pushed today), 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.
Other commands, from other repositories
lavra-work-teams
Work on multiple beads with persistent worker teammates that self-organize through a ready queue.
lavra-retro
Weekly retrospective with shipping analytics, team performance, and knowledge synthesis.
lavra-work-ralph
Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
lavra-quick
Fast-track small tasks — abbreviated plan then straight to execution.
lavra-checkpoint
Save session progress by filing beads, capturing knowledge, and syncing state.