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/versiongit clone --depth 1 https://github.com/gastownhall/beadsWrote 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/gastownhall/beads/version)<a href="https://agentmods.dev/commands/gastownhall/beads/version"><img src="https://agentmods.dev/badge/commands/gastownhall/beads/version.svg" alt="Measured on agentmods" 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 | $0.00005 | $0.00223 |
| Opus 5 | $0.00003 | $0.00112 |
| Sonnet 5 | $0.00001 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade C, and why
version scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Update bd CLI: `curl -fsSL https://raw.githubusercontent.com/gastownhall/beads/main/scripts/install.sh | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Update bd CLI: `curl -fsSL https://raw.githubusercontent.com/gastownhall/beads/main/scripts/install.sh | bash` Copies of this mod
1 near-identical copy found in the catalogue:
- version — 91% identical, 2 lines differ
What it actually says
Check the installed versions of beads components and verify compatibility.
Note: The MCP server automatically checks bd CLI version >= 0.9.0 on startup. This command provides detailed version info and update instructions.
Use the beads MCP tools to:
- Run
bd versionvia bash to get the CLI version - Check the plugin version (0.9.2)
- Compare versions and report any mismatches
Display:
- bd CLI version (from
bd version) - Plugin version (0.9.2)
- MCP server version (0.9.2)
- MCP server status (from
statstool or connection test) - Compatibility status (✓ compatible or ⚠️ update needed)
If versions are mismatched, provide instructions:
- Update bd CLI:
curl -fsSL https://raw.githubusercontent.com/gastownhall/beads/main/scripts/install.sh | bash - Update plugin:
/plugin update beads - Restart Claude Code after updating
Suggest checking for updates if the user is on an older version.
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 · 27 lines · 5 tokens per session scan C f994ab7afb0a
version is a command published in the GitHub repository gastownhall/beads (26,797 stars, last pushed 2d ago), licensed MIT. It adds 5 tokens to every session and 223 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.
lavra-work-ralph
Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.