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 skills add zosmaai/pi-llm-wiki --skill llm-wikigit 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/skills/zosmaai/pi-llm-wiki/llm-wiki)<a href="https://agentmods.dev/skills/zosmaai/pi-llm-wiki/llm-wiki"><img src="https://agentmods.dev/badge/skills/zosmaai/pi-llm-wiki/llm-wiki/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/skills/zosmaai/pi-llm-wiki/llm-wiki"><img src="https://agentmods.dev/badge/skills/zosmaai/pi-llm-wiki/llm-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00052 | $0.04279 |
| Opus 5.5 | $0.00021 | $0.01712 |
| Sonnet 5.5 | $0.00010 | $0.00856 |
| Haiku 4.5 | $0.00005 | $0.00428 |
Grade A, and why
llm-wiki 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 1mo 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLM Wiki for Pi
You are a disciplined wiki maintainer. The extension handles all mechanical work — you focus on synthesis, reasoning, and knowledge organization.
Architecture (4 Layers)
WIKI_ROOT/
└── .llm-wiki/ # All wiki content (one dot-dir)
├── config.json # Vault config
├── templates/ # Page templates
├── raw/sources/SRC-*/ # Immutable source packets (extension-owned)
│ ├── manifest.json
│ ├── original/
│ ├── extracted.md
│ └── attachments/
├── raw/trajectories/TRJ-*/ # Immutable agent task packets (extension-owned)
│ ├── manifest.json # Capture metadata (format: trajectory)
│ ├── packet.json # Full tool-call sequence
│ └── extracted.md # README summary
├── wiki/ # Editable knowledge pages (you own this)
│ ├── sources/ # One summary per source
│ ├── entities/ # People, orgs, tools, products
│ ├── concepts/ # Ideas, patterns, frameworks
│ ├── syntheses/ # Cross-cutting analyses
│ ├── analyses/ # Durable query answers
│ ├── cases/ # One specific past task per trajectory
│ └── skills/ # Reusable patterns distilled from trajectories
├── meta/ # Durable events + generated projections (extension-owned)
│ ├── registry.json # Master page catalog
│ ├── backlinks.json # Inbound link map
│ ├── index.md # Human-readable catalog
│ ├── log.md # Activity log
│ ├── events.jsonl # Structured event stream
│ └── qmd/ # Generated QMD search index (mirrors + SQLite)
├── outputs/ # Generated artifacts
└── .discoveries/ # Discovery tracking
meta/qmd/is extension-owned, generated, and rebuildable withwiki_reindex. It never scanswiki/directly — it indexes parser-valid mirrors. Do not edit individual SQLite/WAL/SHM files insidemeta/qmd/current/; restore the whole directory or rebuild. Active recall still uses the legacy heuristic until Phase 3.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +6 lines 8bd1dc378dc2
- 1mo ago First seen · 324 lines · 52 tokens per session scan A f79666ea67d8
llm-wiki is a skill published in the GitHub repository zosmaai/pi-llm-wiki (615 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 4,279 once invoked, about $0.0002 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 skills, from other repositories
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
wiki-export
Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or OKF bundles. Use when transferring or visualizing wiki data in external tools; wiki-import handles the reverse direction.
llmwiki
Build and use a persistent, citation-traceable knowledge wiki from documents, research papers, notes, or project documentation. Use for llmwiki projects, retrieving reusable evidence for an agent task, or compiling a corpus for repeated questions. A one-off file read or live web search does not need a wiki.
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.