bm

A command for asking basemind questions about a codebase, including its structure, references, history, changes, documents, and saved memories.

In plain words
What is it for?
It is for finding definitions and callers, viewing file outlines, checking recent changes, identifying who edited code, searching repository documents, and recalling stored information.
Why use it?
It provides one natural-language entry point for repository questions instead of manually searching files or running separate code and Git commands.

Command

Install

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.

agentmods
npx agentmods add commands/goldziher/basemind/bm
Clone the repo
git clone --depth 1 https://github.com/Goldziher/basemind
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 466 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.00466
Opus 5 $0.00015 $0.00233
Sonnet 5 $0.00006 $0.00093
Haiku 4.5 $0.00003 $0.00047

Measured 2d ago against content hash 1b2394acc32f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bm 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 2d 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.

.codex-plugin/commands/bm.md · 48 lines

What it actually says

bm — ask basemind anything about this codebase

Answer the user's question using the basemind MCP server instead of reading files or shelling out to grep/git.

When to use

Invoke with a natural-language question about this repo's code, history, or documents — /bm <question>. Use it instead of manually picking a tool when you just want an answer.

How to use

/bm where is MapCache defined?
/bm what calls process_file?
/bm who last touched src/scanner.rs?

Route the question to the tool that answers it directly:

Example question Tool
"Where is X defined?" code mode symbols
"What calls X?" code mode references (any name) or callers (specific definition)
"What's the shape of this file?" code mode outline (add l2: true)
"What changed recently?" git mode recent, touching, or symbol_history
"Who last touched this?" git mode blame or blame_symbol
"Where's the churn?" git mode churn
"Search PDFs/docs in the repo by meaning?" memory mode documents
"Recall something remembered earlier?" memory mode get, list, or search
"Remember this for later sessions?" memory mode put (delete with delete)
"Refresh the index after editing code?" admin mode rescan (paths limits scope)

Notes

  • Answer with paths, line numbers, and signatures — read whole files only after a tool has located the exact span you need.

See also

The basemind skill for the full tool-routing table and context-economy discipline.

Changes

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.

  1. 2d ago First seen · 48 lines · 31 tokens per session scan A 1b2394acc32f

Subscribe to this mod's changes

bm is a command published in the GitHub repository Goldziher/basemind (91 stars, last pushed 6d ago), licensed MIT. It adds 31 tokens to every session and 466 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.