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 skills add Goldziher/basemind --skill basemind-doctorgit 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/skills/goldziher/basemind/basemind-doctor)<a href="https://agentmods.dev/skills/goldziher/basemind/basemind-doctor"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/basemind-doctor/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/skills/goldziher/basemind/basemind-doctor"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/basemind-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.01188 |
| Opus 5 | $0.00034 | $0.00594 |
| Sonnet 5 | $0.00014 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
basemind-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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
basemind-doctor — diagnose and recover basemind
Use this when basemind isn't behaving: MCP tools aren't available or return errors, the
statusline says no index, queries come back empty when they shouldn't, or the basemind serve
MCP server appears dead. Every step here uses the CLI, so it works even when the MCP server is
down.
Important: a stdio MCP server (what basemind serve is) cannot be restarted by an agent or by
basemind itself — a fresh process can't resume the client's MCP initialize handshake.
Reconnecting the server is the MCP client's job (see step 4). What you can do from here is
make sure the index is healthy and clear anything blocking a restart.
1. Is there an index?
basemind admin status
- Errors / "no index" /
file_count: 0with blobs present → the index is missing or lost. Build it:basemind scan(see thebasemind-scanskill //bm-scan). - Healthy
file_count→ the index is fine; the problem is the server connection (step 4).
2. Is a server already running (holding the lock)?
If basemind scan fails with a lock error, a basemind serve (or watch) already owns the index
for this repo. The lock-contention error itself names the live holder (command + pid) — it reads
that from the .lock.meta sidecar next to the workspace .lock. Both live in this workspace's
directory under the machine-global cache (Linux ~/.local/share/basemind/, macOS
~/Library/Application Support/basemind/; override BASEMIND_DATA_HOME), keyed by workspace — not
in the repo.
- If that
pidis alive (ps -p <pid>), the server is up — use the MCP tools, or theadmin { mode: "rescan" }to refresh. Don't run a CLIscan(it will contend on the lock). - If that
pidis dead, the lock is stale. The OS releases the advisory lock when a process dies, so a freshbasemind scan/basemind serveshould just work — retry it. (You may delete the stale.lock.metasidecar in that workspace cache dir to clear the advisory holder record.)
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.
- 9d ago First seen · 88 lines · 69 tokens per session scan A d0ad15a934b9
basemind-doctor is a skill published in the GitHub repository Goldziher/basemind (99 stars, last pushed 7d ago), licensed MIT. It adds 69 tokens to every session and 1,188 once invoked, about $0.0003 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 skills, from other repositories
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
x-ray
Deep codebase exploration using semantic search and relationship mapping. Use when you need to understand the current codebase.
trace-mcp
Use trace-mcp tools for code navigation, impact analysis, and framework-aware queries instead of Read/Grep/Glob/Bash. Activate whenever the agent needs to explore, understand, or modify a codebase that has trace-mcp indexed.
lsp-inspect
Full code quality audit for a file, package, or directory. Supports batch mode (directory walk with --top ranking), comparison mode (--diff for branch-only issues), severity calibration by blast radius, fix suggestions, and confidence tiers. Applies a check taxonomy (dead symbols, silent failures, error wrapping…
lsp-dead-code
Enumerate exported symbols in a file and surface those with zero references across the workspace. Use when auditing for dead code, cleaning up APIs, or checking which exports are safe to remove.
lsp-refactor
End-to-end safe refactor workflow — blast-radius analysis, speculative preview, apply to disk, verify build, run affected tests. Inlines lsp-impact + lsp-safe-edit + lsp-verify + lsp-test-correlation into one coordinated sequence.