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)<a href="https://agentmods.dev/commands/goldziher/basemind/bm"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm/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/commands/goldziher/basemind/bm"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm.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.00031 | $0.00575 |
| Opus 5.5 | $0.00012 | $0.00230 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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 3d 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 — 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.
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.
- 3d ago Changed · +7 lines 26a3bb2511f5
- 1mo ago First seen · 48 lines · 31 tokens per session scan A 1b2394acc32f
bm is a command published in the GitHub repository Goldziher/basemind (112 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 575 once invoked, about $0.0001 per session on Opus 5.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
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
screenshot
Screenshot a URL or document and read it visually.
vios-git
VIOS git conventions: branch names, commit messages, and merge-request descriptions. Use before creating any branch, commit, or MR.
update-vst-ui
Build the VST UI and deploy the static files into the vios tree (services/vios of the video-search-and-summarization repo), both ingress/vst-ui and webroot, then commit.
context-load
Carga de contexto al inicio de sesión. Lee estado del workspace, decisiones recientes, último session save y actividad Git para arrancar con el big picture.
learn
A command that saves reusable discoveries and lessons from a coding session as one-line JSON records. JSONL means one JSON object per line, making the file easy to append to and process.