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-init)<a href="https://agentmods.dev/commands/goldziher/basemind/bm-init"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm-init/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-init"><img src="https://agentmods.dev/badge/commands/goldziher/basemind/bm-init.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.00068 | $0.01492 |
| Opus 5.5 | $0.00027 | $0.00597 |
| Sonnet 5.5 | $0.00014 | $0.00298 |
| Haiku 4.5 | $0.00007 | $0.00149 |
Grade A, and why
bm-init 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bm-init — onboard basemind into this repo
Run basemind init so the repo has a committed basemind.toml and a rules block that tells every
agent to prefer basemind's MCP tools over grep, file reads, and naked git. CLI and slash command
share ONE implementation — this just drives basemind init with the right non-interactive flags.
When to use
First time setting up basemind in a repo, or to refresh the rules block after enabling new capabilities (documents/RAG, agent-comms, semantic search). Safe to re-run: it's idempotent.
How to use
-
Ask which capabilities matter (one short question). The options are:
code-search-navigation,code-mapping-architecture,git-history,agent-comms,documents-rag,semantic-search. If the user has no preference, enable all. -
Ask where the rules block should go — do NOT assume. Never write a committed
CLAUDE.mdorAGENTS.mdwithout the user's explicit say-so. Present the choice:CLAUDE.local.md— personal, gitignored (recommended default)AGENTS.local.md— personal, gitignored (for AGENTS-based tools)CLAUDE.md— committed, shared with everyone on the repoAGENTS.md— committed, shared with everyone on the reponone— write no rules
Exception: if
.ai-rulez/config.tomlis present, ai-rulez owns governance — write the gitignored.ai-rulez/local/rules/basemind-usage.mdinstead of asking (never the committed.ai-rulez/rules/basemind-usage.md, and never CLAUDE.md/AGENTS.md). -
Ask about auto-approving basemind's MCP tools (one short question). basemind can add one
permissions.allowglob entry so Claude Code stops prompting for approval on its own tools. Present the choice:.claude/settings.local.json— personal, gitignored (recommended default).claude/settings.json— committed, shared with everyone on the reponone— skip this step
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 · +8 lines 672b3e48d6af
- 13d ago Changed · +22 lines 44bc988783a9
- 1mo ago First seen · 72 lines · 68 tokens per session scan A e1e0eaa4ae4c
bm-init is a command published in the GitHub repository Goldziher/basemind (112 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 1,492 once invoked, about $0.0003 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
rebase
Data-preserving git rebase and conflict resolution onto v2.1 (or any target branch).
vios-git
VIOS git conventions: branch names, commit messages, and merge-request descriptions. Use before creating any branch, commit, or MR.
review-mr
Fetch all review comments on a GitLab MR, verify each one against the codebase, apply fixes for valid issues, and post a reply to every comment.
vios-release-note
Generate a complete VIOS multi-arch release note for a given build drop version. Fetches container images from GitLab compose.env, GitLab commit titles since the previous release tag, Jira VST tickets, NVBugs entries, Slack channel evidence, and Outlook email evidence, then renders and saves a formatted release note.
why
Why the code is shaped this way — decisions, rationale, and git archaeology (question, path, or decision-health dashboard).
reindex
Rebuild the Repowise vector store by re-embedding all wiki pages. No LLM calls — only embedding API calls.