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/gastownhall/beads/initgit clone --depth 1 https://github.com/gastownhall/beadsWhat 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.00006 | $0.00169 |
| Opus 5 | $0.00003 | $0.00084 |
| Sonnet 5 | $0.00001 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
init 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- init — 100% identical, 2 lines differ
What it actually says
Initialize beads issue tracking in the current directory.
If a prefix is provided as $1, use it as the issue prefix (e.g., "myproject" creates issues like myproject-1, myproject-2). If not provided, the default is the current directory name.
Use the beads MCP init tool with the prefix parameter (if provided) to set up a new beads database.
After initialization:
- Show the database location
- Show the issue prefix that will be used
- Explain the basic workflow (or suggest running
/beads:workflow) - Suggest creating the first issue with
/beads:create
If beads is already initialized, inform the user and show project stats using the stats tool.
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 · 19 lines · 6 tokens per session scan A 975759ee3d7a
init is a command published in the GitHub repository gastownhall/beads (26,797 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 169 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
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
lavra-work-teams
Work on multiple beads with persistent worker teammates that self-organize through a ready queue.
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
lavra-retro
Weekly retrospective with shipping analytics, team performance, and knowledge synthesis.
lavra-setup
Configure project stack, review agents, and workflow settings.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.