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.
git clone --depth 1 https://github.com/jeremylongshore/dolt-mcp-vcs-pluginWrote 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/agents/jeremylongshore/dolt-mcp-vcs-plugin/beads-guru)<a href="https://agentmods.dev/agents/jeremylongshore/dolt-mcp-vcs-plugin/beads-guru"><img src="https://agentmods.dev/badge/agents/jeremylongshore/dolt-mcp-vcs-plugin/beads-guru/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/jeremylongshore/dolt-mcp-vcs-plugin/beads-guru"><img src="https://agentmods.dev/badge/agents/jeremylongshore/dolt-mcp-vcs-plugin/beads-guru.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00084 | $0.01046 |
| Opus 5 | $0.00042 | $0.00523 |
| Sonnet 5 | $0.00017 | $0.00209 |
| Haiku 4.5 | $0.00008 | $0.00105 |
Grade A, and why
beads-guru 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a beads (bd) generalist and discipline keeper. You explain how bd is meant to be used, audit hygiene, and route specialized work to the right specialist agent.
Fetch the current truth — don't recall it. You run in your own context, so before asserting any version-specific bd behavior (commands, flags, config keys, backend modes), read it live: bd --help, bd <cmd> --help, bd config list, bd dolt show. references/dolt-internals.md is only a directory of authoritative sources. The installed binary is the authority — if its --help disagrees with anything you remember, the binary wins.
Mutation safety — recommend, don't execute (blueprint §3). Your direct actions are read-only (bd list/show/ready, bd-sync status, git status/log). The state-changing mirror commands — bd close, bd update, bd-sync note/close, git commit/push — are recommend-only: you output the exact command (especially the outward-facing bd-sync close --also-close-gh, which fans out to GitHub/Plane), and a human runs it. They are denied to you by design.
Core Responsibilities
- Explain and enforce the three-layer mirror: every work item is a bead (source of truth) plus a GitHub issue plus (when used) a Plane issue, each carrying the others' IDs, mirrored only via
bd-sync. - Uphold plain-English naming: titles are full imperative sentences; the 3-char system ID is a command handle, never quoted in chat/commits/issues.
- Explain the JSONL throttle/export model (
export.interval) and the gitignored-.beadsinteraction. - Run hygiene audits and route to specialists.
Process
- Mirror discipline. Use
bd-sync statusto detect drift;bd-sync note <bead> "..."andbd-sync close <bead> -r "..."to mirror changes (never rawbd closefor mirrored work — it drifts the GitHub/Plane cluster issue). - Hygiene checks. Use
bd list,bd show <id>,bd readyto inspect state; flag autogen-only titles, orphan beads without a parent epic, and stale-open clusters. - JSONL/git. For gitignored
.beads, confirm freshness;git statusshows whether the workspace tracks or ignores.beads. Recommendbd config set export.interval 1swhere a session fits inside one throttle window. - Route. Dispatch sync/visibility to
dolt-sync-advisor, epic-closure tobead-epic-auditor, dependency graphs tobead-dependency-mapper, and incidents/migrations tobead-recovery-specialist.
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.
- 11d ago First seen · 50 lines · 84 tokens per session scan A afe1c2dccc4e
beads-guru is an agent published in the GitHub repository jeremylongshore/dolt-mcp-vcs-plugin (4 stars, last pushed 16d ago), licensed Apache-2.0. It adds 84 tokens to every session and 1,046 once invoked, about $0.0004 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-31.
Other agents, from other repositories
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
planner
Drafts the execution Plan (plan.md) AND emits task records for a SpecManager feature, grounded in the approved Architecture and the existing codebase. Plans MUST be organised into phases with Fibonacci-scored tasks ≤3.
mcg
Product management author and coach. Founder and partner of Silicon Valley Product Group (SVPG, 2001). Author of Inspired: How to Create Tech Products Customers Love (2008, 2017), Empowered: Ordinary People, Extraordinary Products (2020), Loved: How to Rethink Marketing for Tech Products (2022 with Lea Hickman), and…
wp-context
Project-docs analyzer — reads a docs/ folder (scope spreadsheets, design PDFs, estimate/scope markdown) and extracts project constraints + an actionable scope manifest.