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/GantisStorm/essentials-claude-codeWrote 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/gantisstorm/essentials-claude-code/beads-swarm)<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/beads-swarm"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/beads-swarm/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/gantisstorm/essentials-claude-code/beads-swarm"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/beads-swarm.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.00010 | $0.01449 |
| Opus 5.5 | $0.00004 | $0.00580 |
| Sonnet 5.5 | $0.00002 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
beads-swarm 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- tasks-swarm — 86% identical, 85 lines differ
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Swarm Command
Execute beads tasks using parallel worker agents. All workers complete → done.
Note: Loop and swarm are interchangeable - swarm is just faster when tasks can run in parallel. Both enforce exit criteria and sync beads.
Uses Claude Code's built-in Task Management System for dependency tracking and visual progress (ctrl+t).
Arguments
--epic <epic-id>(optional): Filter beads by epic--label <label>(optional): Filter beads by label (default:ralph)--workers N(optional): Max concurrent workers (default: 3)--model MODEL(optional): Model for workers: haiku, sonnet, opus (default: sonnet)
Instructions
Step 1: Load Beads (Only)
DO NOT read files, grep, or explore the codebase - just get beads from CLI:
bd list --status open --json
# Or with filters:
bd list --epic <epic-id> --status open --json
bd list -l <label> --status open --json
Parse the output to get all beads.
Step 2: Create Task Graph
Create a task for each bead and build an ID map as you go:
// Create tasks in order — each returns a task ID
TaskCreate({ "subject": "beads-abc123: Setup types", ... }) // → task "1"
TaskCreate({ "subject": "beads-def456: Implement auth", ... }) // → task "2"
TaskCreate({ "subject": "beads-ghi789: Add routes", ... }) // → task "3"
// ID map: { "beads-abc123": "1", "beads-def456": "2", "beads-ghi789": "3" }
Full TaskCreate per bead:
TaskCreate({
"subject": "beads-abc123: Implement login form",
"description": "<full bead description - self-contained>",
"activeForm": "Implementing login form",
"metadata": { "beadId": "beads-abc123" }
})
Translate bead dependencies to addBlockedBy using the ID map. Extract depends_on from bd list --json output:
// bd list shows: beads-ghi789 depends_on ["beads-abc123", "beads-def456"]
// ID map: beads-abc123→"1", beads-def456→"2", beads-ghi789→"3"
TaskUpdate({
"taskId": "3",
"addBlockedBy": ["1", "2"]
})
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 · 142 lines · 10 tokens per session scan A 2cdc1c70100c
beads-swarm is a command published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 10 tokens to every session and 1,449 once invoked, about $0.0000 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 commands, from other repositories
report-issue-with-atomic
Open an issue against the atomic-claude repo itself (bugs/feature requests with the installed config, not the user's current project).
report-issue
Open a atomic GitHub issue via gh. Bug report or feature request — auto-detect from user's description.
feature-config
Phase 0 of develop: Configuration wizard, escape hatches, preferences, continuation detection.
specmanager-build
Build one phase of a SpecManager feature's plan via the builder subagent. Stops at the phase boundary; never advances.
polish-repo-community
Phase 3 of polish-repo: Community infrastructure, issue templates, roadmap, contributor experience, and signs of life.
create-issue
Create a GitHub issue with proper template discovery and population.