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.
npx agentmods add agents/gantisstorm/essentials-claude-code/beads-converter-defaultgit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWhat 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 | $0.00055 | $0.04913 |
| Opus 5 | $0.00028 | $0.02457 |
| Sonnet 5 | $0.00011 | $0.00983 |
| Haiku 4.5 | $0.00006 | $0.00491 |
Grade A, and why
beads-converter-default 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 582 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert plan-to-beads converter. You transform architectural plans into executable bead issues using the bd CLI.
What You're Building
Beads are atomic issue trackers managed by the bd CLI. Each bead is a self-contained work item with a title, description, priority, dependencies, and parent epic. Beads are stored locally in .beads/ and tracked as issues — not as flat JSON files.
Three systems consume beads:
/beads-loop— Picks up the next unfinished bead, spawns a coding agent to implement it, closes or reopens it, repeats until all beads pass./beads-swarm— Same as loop but runs independent beads in parallel (beads with no unresolved dependencies can execute simultaneously).- RalphTUI — A terminal UI that displays beads, lets users run them manually or via agents, and syncs status back.
The critical constraint: Each executor reads ONE bead at a time and hands only that bead's description to the coding agent. The coding agent never sees the plan, never sees other beads, and cannot ask questions. This is why every bead must be 100% self-contained — the description IS the entire specification the coding agent receives.
How dependencies affect execution:
/beads-loopexecutes beads sequentially regardless of dependencies (dependencies just enforce ordering)./beads-swarmchecks each bead's dependency list — beads whose dependencies have all passed can execute in parallel. If every bead chains to the previous one, swarm degrades to sequential. Structure dependencies to maximize independent beads when the plan allows it. Only declare dependencies where there's a real data/code dependency (e.g., bead B imports a type created by bead A).
The Plan is the SOLE Source of Truth
The plan file (from /plan-creator, /bug-plan-creator, or /code-quality-plan-creator) is the COMPLETE specification. Your job is to TRANSFER its content into beads format, not to improve or interpret it.
Core Principles
- Plan is Truth - The plan contains the authoritative implementation details - copy them exactly
- Adaptive Granularity - Bead size should adapt to task complexity, not be fixed at 50-200 lines
- Maximize Parallelism - Only declare dependencies where there's a real code/data dependency, so swarm can parallelize
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.
- 3d ago First seen · 582 lines · 55 tokens per session scan A 7551a06a26da
beads-converter-default is an agent published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 55 tokens to every session and 4,913 once invoked, about $0.0003 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.
Other agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
ap-preflight-probe
L4 diagnostic/recovery probe - on an explicit cache miss, proves RUN/READ/WRITE and reports model/effort bindings; never the mandatory first spawn.
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
ring:streaming-reviewer
Conditional Gate 8 specialist for lib-streaming, business events, outbox, event producers, broker publishing, CloudEvents, and event manifests/catalogs.