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-statuslinegit 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-statusline)<a href="https://agentmods.dev/commands/goldziher/basemind/bm-statusline"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm-statusline.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.00022 | $0.00770 |
| Opus 5 | $0.00011 | $0.00385 |
| Sonnet 5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade B, and why
bm-statusline scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. **Update `~/.claude/settings.json`** (treat a missing file as `{}`). Set its How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bm-statusline — enable the basemind status line
Wire the basemind status line into the user's global Claude Code settings, then confirm it renders.
When to use
Run this once per machine to enable the basemind status line in Claude Code. Re-run only if the bar goes blank after an unusual settings edit.
How to use
Invoke /bm-statusline. Use your tools to do this directly — do not ask the user to hand-edit
any files.
-
Confirm the plugin is installed. Check that at least one of these exists:
${CLAUDE_PLUGIN_ROOT}/.claude-plugin/statusline.sh(if that var is set)~/.claude/plugins/marketplaces/basemind/.claude-plugin/statusline.sh- a match of
~/.claude/plugins/cache/basemind/basemind/*/.claude-plugin/statusline.sh
If none exists, tell the user the basemind plugin isn't installed and stop.
-
Update
~/.claude/settings.json(treat a missing file as{}). Set itsstatusLinekey to this version-independent resolver — do NOT hardcode a version-pinned path, which breaks on the next basemind update when the old version dir is pruned:{ "type": "command", "command": "bash -c 's=$(ls -d \"$HOME\"/.claude/plugins/cache/basemind/basemind/*/.claude-plugin/statusline.sh 2>/dev/null | sort -V | tail -1); [ -f \"$s\" ] || s=\"$HOME/.claude/plugins/marketplaces/basemind/.claude-plugin/statusline.sh\"; [ -f \"$s\" ] && exec bash \"$s\" || printf \"%s\" \"◆ basemind: run /bm-statusline\"'", "refreshInterval": 5 }How it resolves, in order: the highest-versioned cached copy (
sort -V, not mtime — an older dir touched more recently must never win; this also makes the bar track the newest version the moment/plugin updateinstalls it), else the marketplace clone, else a one-line hint so the bar is never blank. It re-resolves at every render, so version bumps never break it and script improvements land automatically. Copy thecommandstring verbatim (it self-resolves —$HOMEis expanded by thebash -cit runs under, not the settings field). Preserve every other key and verify the file is still valid JSON afterward.
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.
- 5d ago First seen · 58 lines · 22 tokens per session scan B eb6402e7f866
bm-statusline is a command published in the GitHub repository Goldziher/basemind (98 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 770 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
dream
Memory dream pass — judge undreamed days, promote durable signal to long-term, then sweep.