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/6eanut/llm-wiki/wiki-savegit clone --depth 1 https://github.com/6eanut/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/6eanut/llm-wiki/wiki-save)<a href="https://agentmods.dev/commands/6eanut/llm-wiki/wiki-save"><img src="https://agentmods.dev/badge/commands/6eanut/llm-wiki/wiki-save.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.00012 | $0.00150 |
| Opus 5 | $0.00006 | $0.00075 |
| Sonnet 5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
wiki-save 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 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.
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
Save Answer as Synthesis Page
The user ran /wiki-save $ARGUMENTS.
This saves the current conversation answer as a permanent synthesis page in the wiki. This is the compounding mechanism — good answers become part of the knowledge base.
Procedure
Use Skill("llm-wiki") → workflows/save-synthesis.md for the full procedure:
- Identify the query and answer from conversation context
- Create
synth-YYYY-MM-DD-{slug}.mdusing the synthesis template - Cross-link to all source pages via
based_on - Regenerate the index
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 · 19 lines · 12 tokens per session scan A b54020dcf3d7
wiki-save is a command published in the GitHub repository 6eanut/llm-wiki (43 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 150 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
contribute
Add a thought, source, or paste. Use --project/-p to target another project without switching current. Usage: /mb:contribute [-p ] [--mode daily|concept|daily+concept].
build
Rebuild context.md for a project from sources/. Usage: /mb:build [-p ] [project-id].
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
research
Deep research on a topic — web + existing wiki + synthesis → sources/research/. Usage: /mb:research [-p ].
new-project
Create a new project with template choice — interactive flow. Usage: /mb:new-project [template].
ask
Query the MindBase wiki — cited answer using hybrid search + graph expansion. Usage: /mb:ask [-p ] [--all-projects].