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/labelgit 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.00003 | $0.00250 |
| Opus 5 | $0.00002 | $0.00125 |
| Sonnet 5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
label 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- label — 100% identical, 2 lines differ
What it actually says
Manage labels on beads issues. Labels provide flexible cross-cutting metadata beyond structured fields (status, priority, type).
Available Commands
-
add: Add a label to an issue
- $1: "add"
- $2: Issue ID
- $3: Label name
-
remove: Remove a label from an issue
- $1: "remove"
- $2: Issue ID
- $3: Label name
-
list: List labels on a specific issue
- $1: "list"
- $2: Issue ID
-
list-all: Show all labels used across all issues
Common Label Use Cases
- Technical scope:
backend,frontend,api,database - Quality gates:
needs-review,needs-tests,security-review - Effort sizing:
quick-win,complex,spike - Context:
technical-debt,documentation,performance
Use bd label add <issue-id> <label> to tag issues with contextual metadata.
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 · 34 lines · 3 tokens per session scan A 45f0422cce87
label is a command published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It adds 3 tokens to every session and 250 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-retro
Weekly retrospective with shipping analytics, team performance, and knowledge synthesis.
lavra-work-ralph
Autonomous retry mode for bead work -- iterates until completion criteria are met or retry budget is exhausted.
lavra-qa
Browser-based QA verification of the running app -- systematic testing from the user's perspective.
lavra-ship
Fully automated ship sequence from code-ready to PR-open with beads closed and knowledge captured.