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/reset-beads)<a href="https://agentmods.dev/commands/gantisstorm/essentials-claude-code/reset-beads"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/reset-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/gantisstorm/essentials-claude-code/reset-beads"><img src="https://agentmods.dev/badge/commands/gantisstorm/essentials-claude-code/reset-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.00014 | $0.00305 |
| Opus 5.5 | $0.00006 | $0.00122 |
| Sonnet 5.5 | $0.00003 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
reset-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
Reset Beads
Reopen all tasks in a beads epic so they can be re-run from the beginning.
Instructions
If epic ID provided:
Get all child tasks (including closed) and reopen them:
bd list --parent <epic-id> --all --json | jq -r '.[].id' | xargs -I {} bd reopen {} --reason "Reset for re-run"
If --label provided:
Get all tasks with that label (including closed) and reopen them:
bd list -l <label> --all --json | jq -r '.[].id' | xargs -I {} bd reopen {} --reason "Reset for re-run"
If no argument:
List recent epics for the user to choose:
bd list --type epic -n 10
Then ask which epic to reset.
After resetting, tell the user they can run: /beads-loop or /beads-swarm (with optional --label <label>)
Note: Loop and swarm are interchangeable—swarm is just faster when tasks can run in parallel. Both enforce exit criteria and sync.
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 · 44 lines · 14 tokens per session scan A 121335a17a3c
reset-beads is a command published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 14 tokens to every session and 305 once invoked, about $0.0001 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.