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 agentmods add commands/goldziher/basemind/bm-scangit 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-scan)<a href="https://agentmods.dev/commands/goldziher/basemind/bm-scan"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm-scan.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 | $0.00047 | $0.00377 |
| Opus 5 | $0.00023 | $0.00188 |
| Sonnet 5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
bm-scan 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 4d 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-scan — build or refresh the basemind index
Run basemind scan via the CLI so the code map exists and is current.
When to use
basemind (or its statusline) reports "no index" / "no indexed files", an MCP tool returns empty results that shouldn't be empty, or the index is stale after large changes.
How to use
basemind scan ${ARGUMENTS:-}
- No argument → full working-tree scan.
- A path argument (
/bm-scan src/mcp) → scope the scan to that path (incremental). - If
basemindisn't onPATH: use the plugin-managed cache (${XDG_CACHE_HOME:-~/.cache}/basemind/bin/<version>/basemind), or build a dev binary withcargo build --releaseand use./target/release/basemind.
Notes
- Report files scanned / updated / skipped and elapsed time. Non-extractable files are skipped, not failures.
- If a
basemind serveMCP server already holds the store lock for this repo,scanerrors on the lock — useadmin { mode: "rescan" }over MCP instead, or stop the server first.
See also
The basemind-scan skill for the full workflow, binary-resolution order, and extra_roots
config for indexing directories outside the repo.
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.
- 4d ago First seen · 39 lines · 47 tokens per session scan A 87b14366c071
bm-scan is a command published in the GitHub repository Goldziher/basemind (91 stars, last pushed 8d ago), licensed MIT. It adds 47 tokens to every session and 377 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
rb-ask
Ask a question about the current project's codebase via the repobrain knowledge hub. / 通过 repobrain 知识库询问当前项目代码。.
rb-refresh
Rebuild the repobrain project knowledge base after significant changes. / 在重要改动后重建 repobrain 项目知识库。.
coverage
Ingest or inspect test-coverage reports — LCOV, Cobertura/Clover, or coverage.py .coverage (builds the per-test map when contexts are present).
doctor
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
init
Set up Repowise for this codebase. Installs if needed, asks about your preferences, and runs the indexing.
codesage-review
Review CodeSage feature slices in parallel and persist validated findings.