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/zosmaai/pi-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/zosmaai/pi-llm-wiki/wiki-status)<a href="https://agentmods.dev/commands/zosmaai/pi-llm-wiki/wiki-status"><img src="https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-status/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/zosmaai/pi-llm-wiki/wiki-status"><img src="https://agentmods.dev/badge/commands/zosmaai/pi-llm-wiki/wiki-status.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.00018 | $0.00109 |
| Opus 5 | $0.00009 | $0.00055 |
| Sonnet 5 | $0.00004 | $0.00022 |
| Haiku 4.5 | $0.00002 | $0.00011 |
Grade A, and why
wiki-status 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 9d 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
/wiki-status
Show a quick overview of wiki health and statistics.
Steps
- Call
wiki_status()to get the current wiki health report. - Present the results to the user.
- If health shows warnings (orphans > 5, many gaps), suggest running
/wiki-lintfor a detailed analysis.
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.
- 9d ago First seen · 17 lines · 18 tokens per session scan A a9287ad1e181
wiki-status is a command published in the GitHub repository zosmaai/pi-llm-wiki (562 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 109 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
build
Rebuild context.md for a project from sources/. Usage: /mb:build [-p ] [project-id].
lint
Run health check on a project — orphans, contradictions, stale claims, gaps, suggested cross-links. Usage: /mb:lint [-p ] [project-id].
ask
Query the MindBase wiki — cited answer using hybrid search + graph expansion. Usage: /mb:ask [-p ] [--all-projects].
load
Explicitly load a project's context into session (overrides SessionStart hook). Usage: /mb:load [project-id].
init_newbrain
Onboarding interativo que personaliza AGENTS.md, Memória/ e a estrutura inicial do vault.
vault_gc
Manutenção semanal do vault: arquiva handovers antigos, valida Memória/INDEX.md e triage do INBOX.