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/statsgit 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/stats)<a href="https://agentmods.dev/commands/gastownhall/beads/stats"><img src="https://agentmods.dev/badge/commands/gastownhall/beads/stats.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.00137 |
| Opus 5 | $0.00003 | $0.00068 |
| Sonnet 5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
stats 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 4d 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:
- stats — 100% identical, 0 lines differ
What it actually says
Display statistics about the current beads project.
Use the beads MCP stats tool to retrieve project metrics and present them clearly:
- Total issues by status (open, in_progress, blocked, closed)
- Issues by priority level
- Issues by type (bug, feature, task, epic, chore)
- Completion rate
- Recently updated issues
Optionally suggest actions based on the stats:
- High number of blocked issues? Run
/beads:blockedto investigate - No in_progress work? Run
/beads:readyto find tasks - Many open issues? Consider prioritizing with
/beads:update
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.
- 4d ago First seen · 18 lines · 5 tokens per session scan A f4da8a61fb79
stats is a command published in the GitHub repository gastownhall/beads (26,853 stars, last pushed today), licensed MIT. It adds 5 tokens to every session and 137 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-work-ralph
Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.
lavra-import
Import a markdown plan into beads as an epic with child tasks.
code-review
Command "code-review" from alisunstar/OpenSunstar, covering /rd:code-review — 代码审查, 先读, 执行, 产物 and 人工确认.
clarify
Command "clarify" from alisunstar/OpenSunstar, covering /rd:clarify — 澄清, 先读, 执行, 产物 and 人工确认.