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/depgit 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.00004 | $0.00873 |
| Opus 5 | $0.00002 | $0.00436 |
| Sonnet 5 | $0.00001 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
dep 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:
- dep — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage dependencies between beads issues.
Available Commands
-
add: Add a dependency between issues
- $1: "add"
- $2: From issue ID
- $3: To issue ID
- $4: Dependency type (blocks, related, parent-child, discovered-from)
-
remove: Remove a dependency
- $1: "remove"
- $2: From issue ID
- $3: To issue ID
-
tree: Show dependency tree for an issue
- $1: "tree"
- $2: Issue ID
- Flags:
--reverse: Show dependent tree (what was discovered from this) instead of dependency tree (what blocks this)--format mermaid: Output as Mermaid.js flowchart (renders in GitHub/GitLab markdown)--json: Output as JSON--max-depth N: Limit tree depth (default: 50)--show-all-paths: Show all paths (no deduplication for diamond dependencies)
-
cycles: Detect dependency cycles
Dependency Types
- blocks: Hard blocker (from blocks to) - affects ready queue
- related: Soft relationship - for context only
- parent-child: Epic/subtask relationship
- discovered-from: Track issues found during work
Mermaid Format
The --format mermaid option outputs the dependency tree as a Mermaid.js flowchart:
Example:
bd dep tree bd-1 --format mermaid
Output can be embedded in markdown:
```mermaid
flowchart TD
bd-1["◧ bd-1: Main task"]
bd-2["☑ bd-2: Subtask"]
bd-1 --> bd-2
```
Status Indicators:
Each node includes a symbol indicator for quick visual status identification:
- ☐ Open - Not started yet (empty checkbox)
- ◧ In Progress - Currently being worked on (half-filled box)
- ⚠ Blocked - Waiting on something (warning sign)
- ☑ Closed - Completed! (checked checkbox)
The diagram colors are determined by your Mermaid theme (default, dark, forest, neutral, or base). Mermaid diagrams render natively in GitHub, GitLab, VSCode markdown preview, and can be imported to Miro.
Examples
bd dep add bd-10 bd-20 --type blocks: bd-10 depends on bd-20 (bd-20 blocks bd-10)bd dep tree bd-20: Show what blocks bd-20 (dependency tree going UP)bd dep tree bd-1 --reverse: Show what was discovered from bd-1 (dependent tree going DOWN)bd dep tree bd-1 --reverse --max-depth 3: Show discovery tree with depth limitbd dep tree bd-20 --format mermaid > tree.md: Generate Mermaid diagram for documentationbd dep cycles: Check for circular dependencies
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 · 102 lines · 4 tokens per session scan A 2d50ea5c65e0
dep is a command published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It adds 4 tokens to every session and 873 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.