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/frankchu91/mindbase-llm-wiki/initgit clone --depth 1 https://github.com/frankchu91/mindbase-llm-wikiWrote 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/frankchu91/mindbase-llm-wiki/init)<a href="https://agentmods.dev/commands/frankchu91/mindbase-llm-wiki/init"><img src="https://agentmods.dev/badge/commands/frankchu91/mindbase-llm-wiki/init.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.00028 | $0.00363 |
| Opus 5 | $0.00014 | $0.00181 |
| Sonnet 5 | $0.00006 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
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 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
Scaffold a new MindBase project.
Arguments: $ARGUMENTS
Parse:
- First positional token = project name (required).
- Optional
--template <name>(default:empty). Allowed:empty,investigation,literature-review,market-research,reading-companion,topic-tracker. - Optional
--mission "<one-liner>".
If $ARGUMENTS is empty, ask the user:
- What's the project name?
- (Optional) Which template? List the 6 options above.
- (Optional) One-line mission?
Then call mindbase_init_project({ name, template, mission }). The tool will:
- Slugify name → projectId.
- Create
~/mindbase-data/projects/<projectId>/{README.md, context.md, index.yaml, sources/contributors/, sources/research/, sources/raw/, state/, logs/, artifacts/}. - Refuse if the project already exists.
After success, also write currentProjectId into ~/mindbase-data/config.json using mindbase_load_project (or write directly if config.json doesn't exist yet) so subsequent sessions auto-load this project.
Report to user:
✓ Project '<projectId>' created at <projectRoot>
Files: README.md, context.md, index.yaml, logs/<today>.md
Now run /mb:contribute to add your first thought.
MindBase is in early beta — feedback & bugs: https://github.com/frankchu91/mindbase/issues (maintainer replies same-day)
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 · 34 lines · 28 tokens per session scan A a969d43b3edf
init is a command published in the GitHub repository frankchu91/mindbase-llm-wiki (93 stars, last pushed 10d ago), licensed MIT. It adds 28 tokens to every session and 363 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
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-ingest
Process new source packets and synthesize them into wiki knowledge pages.
wiki-record
Capture the just-completed task's tool-call trajectory into the wiki as agent working-memory, then optionally distill it into a reusable skill.
wiki-retro
Save an atomic insight from the current task into the wiki. Creates a single markdown file that layered recall surfaces in future sessions.
wiki-run
Run the full wiki cycle: discover → ingest → lint. Optionally schedule for auto-updates.