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 commands/gantisstorm/essentials-claude-code/beads-loopgit 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.00008 | $0.01228 |
| Opus 5 | $0.00004 | $0.00614 |
| Sonnet 5 | $0.00002 | $0.00246 |
| Haiku 4.5 | $0.00001 | $0.00123 |
Grade A, and why
beads-loop 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.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Beads Loop Command
Execute beads iteratively until all ready tasks are complete.
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
--label <label>(optional): Filter beads by label (default:ralph)--max-iterations N(optional): Maximum iterations before stopping (default: unlimited)
Instructions
Step 1: Load Beads (Only)
DO NOT read files, grep, or explore the codebase - just get beads from CLI. Never spawn sub-agents or delegate work — do ALL implementation directly yourself.
bd list --status open --json
# Or with filters:
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"]
})
A task with non-empty blockedBy shows as blocked in ctrl+t. When a blocking task is marked completed, it's automatically removed from the blocked list. A task becomes ready (executable) when its blockedBy list is empty.
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.
- yesterday First seen · 156 lines · 8 tokens per session scan A fef8b29aa526
beads-loop is a command published in the GitHub repository GantisStorm/essentials-claude-code (91 stars, last pushed 6mo ago), licensed Unlicense. It adds 8 tokens to every session and 1,228 once invoked, about $0.0000 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 commands, from other repositories
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
version
Display current guide and Claude Code versions.
go-review
Go code review for idiomatic patterns.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
execute
Executa o plano aprovado em .first-plan/07-state/plans/. Segue o plano à risca, para se algo invalidar premissa, gera relatório ao final.