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/scangit clone --depth 1 https://github.com/Goldziher/basemindWhat 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.00016 | $0.00226 |
| Opus 5 | $0.00008 | $0.00113 |
| Sonnet 5 | $0.00003 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
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 2d 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
Scan
Run a full basemind scan and report the result.
-
Build if stale:
cargo build --release(skip iftarget/release/basemindis fresh). -
Run:
./target/release/basemind scan ${1:-.} -
Report from stdout / the resulting
.basemind/:- Wall-clock scan time.
- Total files indexed.
- Total symbols extracted.
- Whether eager L2 was active (check
.ai-rulez-equivalent config:eager_l2inbasemind.tomlor defaulttrue).
-
If scan time exceeds the baseline for the repo size by > 20%, flag the regression.
This command exists to drive perf iteration loops — pair it with /harden to confirm no regression on the canary repos.
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.
- 2d ago First seen · 27 lines · 16 tokens per session scan A 289fe87d53e6
scan is a command published in the GitHub repository Goldziher/basemind (91 stars, last pushed 7d ago), licensed MIT. It adds 16 tokens to every session and 226 once invoked, about $0.0001 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-setup
First-time setup. Configure the LLM API key, or a no-API-key local host runner (Codex / Trae / Claude / any headless CLI) that RepoBrain uses for codebase Q&A and refresh. / 首次 setup，配置 RepoBrain 代码问答与 refresh 所需的 LLM API key，或无需 API key 的本地 host runner（Codex / Trae / Claude / 任意无头 CLI）。.
why
Why the code is shaped this way — decisions, rationale, and git archaeology (question, path, or decision-health dashboard).
search
Search the Repowise wiki using natural language, full-text, or symbol search.
vitaecontext-cv
Audit or improve a CV for ATS-safe personal branding SEO.
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
vitaecontext-linkedin
Audit or improve LinkedIn profile positioning and discoverability.