Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/GantisStorm/essentials-claude-codenpx agentmods add agents/gantisstorm/essentials-claude-code/beads-converter-defaultWrote 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/agents/gantisstorm/essentials-claude-code/beads-converter-default)<a href="https://agentmods.dev/agents/gantisstorm/essentials-claude-code/beads-converter-default"><img src="https://agentmods.dev/badge/agents/gantisstorm/essentials-claude-code/beads-converter-default/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/agents/gantisstorm/essentials-claude-code/beads-converter-default"><img src="https://agentmods.dev/badge/agents/gantisstorm/essentials-claude-code/beads-converter-default.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.00055 | $0.04913 |
| Opus 5.5 | $0.00022 | $0.01965 |
| Sonnet 5.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 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.
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.
- 1mo 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 (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 55 tokens to every session and 4,913 once invoked, about $0.0002 per session on Opus 5.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
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.
prd-writer
Drafts a PRD (Product Requirements Document) for a SpecManager feature. Interviews the user briefly when needed and writes the draft straight to disk via the createdocument MCP tool.
jira-mutator
Use for Atlassian/Jira write operations via scoped Atlassian MCP write tools — create issue, transition status, add comment, edit fields. Operator confirmation is REQUIRED for every state transition (and any other mutation that changes issue state). Jira access uses runtime-discovered Atlassian MCP write tools; the…
jira-reader
Use for read-only Atlassian/Jira inspection — fetching issues, comments, sprints, and project metadata via Atlassian MCP read tools. Performs no mutations. Jira access uses runtime-discovered Atlassian MCP read tools; the tools: frontmatter narrows declarable tools to Read. Returns structured JSON.
emperor-governor
Resource governance agent. Use to track scope creep, token usage, and project drift. The Emperor's gaze is fixed on the finite—budgets, time, focus. Invoke when: project feels bloated, need objective scope assessment, tracking resource consumption.
backlog-verifier
Decides, for each backlog entry in one dispatched chunk, whether the thing it describes is still true — one verdict and one evidence line per row, read-only.