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/exportgit 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.00199 |
| Opus 5 | $0.00003 | $0.00100 |
| Sonnet 5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
export 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.
What it actually says
Export all issues to JSON Lines format (one JSON object per line).
Usage
- To stdout:
bd export - To file:
bd export -o issues.jsonl - Include all records:
bd export --all -o full.jsonl
Issues are sorted by ID for consistent diffs, making git diffs readable.
When to Use
Dolt is the primary storage backend, so manual export is rarely needed. Use bd export when you need:
- A JSONL snapshot of issue records
- Data migration to another system
- Sharing issues outside the Dolt workflow
bd export is not a full database backup. It does not capture Dolt branches,
commit history, working-set state, or non-issue tables. Use bd backup for a
restorable Dolt-native database backup.
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 · 26 lines · 6 tokens per session scan A 5c8e9c9b4df7
export 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 199 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.
hatch3r-api-spec
Generate or validate an OpenAPI specification from the codebase. Scans route definitions, extracts schemas, and produces a complete API spec.
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
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.