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-statsgit 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-stats)<a href="https://agentmods.dev/commands/goldziher/basemind/bm-stats"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm-stats.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.00040 | $0.00524 |
| Opus 5 | $0.00020 | $0.00262 |
| Sonnet 5 | $0.00008 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00052 |
Grade A, and why
bm-stats 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-stats — basemind dashboard
Show a basemind dashboard with two sections: resource footprint (on-disk size + process RAM) and activity (tool calls, per-tool histogram, estimated tokens saved).
When to use
The user asks "how much is basemind helping?", "show me basemind stats", or wants to check disk / RAM usage.
How to use
Invoke /bm-stats (default window today) or /bm-stats <today|1h|24h|all>. Window: $ARGUMENTS
-
Resource footprint. MCP
admin { mode: "cache_stats" }, or CLIbasemind admin cache-stats(add--jsonto parse). Report:total_bytes(matchesdu), the per-component breakdown (blobs / views / git-history / lance / git-cache / telemetry / other), and process RAM (rss_bytes+peak_rss_bytes). Ifblob_accounting_okisfalse, note that orphan accounting was skipped (stale/unreadable index — re-scan to restore it); the sizes are still accurate. -
Activity. MCP
admin { mode: "telemetry", window: "…" }, or CLIbasemind admin telemetry --window <today|1h|24h|all>(add--json). Report call count, the per-tool histogram, and estimated tokens saved for the window. -
Render both sections as a compact markdown dashboard.
Notes
- Prefer MCP when connected, but don't depend on it — the CLI reads the same data with no server.
If an
adminmode isn't available, run its CLI equivalent instead of giving up. - If neither MCP nor CLI is reachable, say so plainly and point at
/bm-doctor. - Always end with a one-sentence disclosure that the savings number is heuristic: tools without a realistic baseline (memory, document search, git wrappers) report 0 saved.
See also
The basemind-stats skill for the render shape and the --explain breakdown.
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 First seen · 45 lines · 40 tokens per session scan A 9df7e30d6c62
bm-stats is a command published in the GitHub repository Goldziher/basemind (91 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 524 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.