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/Goldziher/basemindWrote 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/goldziher/basemind/bm-doctor)<a href="https://agentmods.dev/commands/goldziher/basemind/bm-doctor"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm-doctor.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.1 | $0.00045 | $0.00317 |
| Opus 5 | $0.00023 | $0.00159 |
| Sonnet 5 | $0.00009 | $0.00063 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
bm-doctor 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 7d 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
bm-doctor — diagnose and recover basemind
Diagnose and recover basemind using the CLI (works even with no MCP server running).
When to use
basemind isn't behaving: MCP tools are missing or erroring, the statusline or a tool reports
"no index" / "no indexed files", results are empty when they shouldn't be, or the basemind serve MCP server seems dead.
How to use
Invoke /bm-doctor (optional free-text detail, e.g. /bm-doctor tools return no indexed files).
It runs the checks below in order:
- Check the index:
basemind admin status. - Check for a lock-holding server:
cat .basemind/.lock.meta. - Rebuild the index if needed:
basemind scan. - Reconnect the MCP server (client-specific — this is the only way to restart it).
Notes
- A stdio MCP server can't be restarted by an agent or by basemind itself; reconnecting it is the MCP client's job. The CLI stays usable throughout.
See also
The basemind-doctor skill for the full step-by-step diagnostic workflow, lock-holder detection,
and log-reading guidance.
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.
- 7d ago First seen · 35 lines · 45 tokens per session scan A 8098d1650921
bm-doctor is a command published in the GitHub repository Goldziher/basemind (98 stars, last pushed 5d ago), licensed MIT. It adds 45 tokens to every session and 317 once invoked, about $0.0002 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
ask
Ask a codebase question and get a cited, synthesised answer with a confidence rating (costs an LLM call).
context
Triage card for files, modules, or symbols — layer, hotspot, fix history, freshness (relationships, not source bytes).
dead-code
Report unreachable files, unused exports, and zombie packages, tiered by confidence.
doctor
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
codesage-reindex
Force an incremental codesage re-index (use when git hooks didn't fire). Auto-cleans orphan vec tables if the config model has changed.
codesage-reset
Drop a project's CodeSage index and rebuild from scratch (use after settings changes, device switches, or corruption).