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 Oshayr/LLM-Wiki --skill readgit clone --depth 1 https://github.com/Oshayr/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/oshayr/llm-wiki/read)<a href="https://agentmods.dev/skills/oshayr/llm-wiki/read"><img src="https://agentmods.dev/badge/skills/oshayr/llm-wiki/read/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/oshayr/llm-wiki/read"><img src="https://agentmods.dev/badge/skills/oshayr/llm-wiki/read.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.00102 | $0.00746 |
| Opus 5.5 | $0.00041 | $0.00298 |
| Sonnet 5.5 | $0.00020 | $0.00149 |
| Haiku 4.5 | $0.00010 | $0.00075 |
Grade A, and why
wiki-read 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 2mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Read
Ask the wiki a question and get a cited answer. If the wiki doesn't have the answer, automatically researches using whatever tools are available, ingests the results, and answers from the new pages.
Resolve .wiki/ from plugin install scope. If not found, say "No wiki found. Use /wiki-write to create one."
Arguments
/wiki-read <question>— standard: search wiki first, research if not found, answer with citations/wiki-read quick <question>— index scan only, no research fallback (fastest)/wiki-read deep <question>— full wiki search + raw sources + automatic multi-channel research if needed (most thorough)
Process
Launch the wiki-reader agent with the question and depth level.
Standard depth (default)
- Read
.wiki/index.md, identify 2-4 relevant pages - Use
bin/search-fulltext.pyfor ranked results - Read the relevant pages, synthesize a cited answer with
[[slug]]references - If NOT found or insufficient: automatically research using whatever tools are available:
- Discover available tools at runtime (WebSearch, WebFetch,
wiki_wikipedia_searchfor factual/encyclopedic topics, any MCP tools like Perplexity, Context7, etc.) - Search using available tools, fetch and extract content
- Ingest results via
wiki-writeragent (mode: ingest) - Answer from the newly created pages with
[[slug]]citations - Note: "Researched fresh and saved to wiki."
- Discover available tools at runtime (WebSearch, WebFetch,
- Offer to save analysis as a wiki page if the answer is substantial
Quick depth
- Read
.wiki/index.mdonly - Scan for matching slugs/titles by text match
- Return: list of relevant pages with one-line descriptions
- No page content read, no research fallback — fastest possible response
- If not found, suggest running standard
/wiki-read
Deep depth
Everything in standard, plus:
- Search
.wiki/raw/for source materials matching the query - Cross-reference raw sources with compiled pages
- Use all available tools iteratively for multi-channel research if needed
- Most thorough — uses the most context
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.
- 2mo ago First seen · 60 lines · 102 tokens per session scan A 0aeaed29e18d
wiki-read is a skill published in the GitHub repository Oshayr/LLM-Wiki (50 stars, last pushed 6mo ago), licensed MIT. It adds 102 tokens to every session and 746 once invoked, about $0.0004 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.
wiki-read compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| wiki-readOshayr/LLM-Wiki | Skill | 50 | 6mo ago | MIT | A | 102 | Claude Code |
| llm-wikipraneybehl/llm-wiki-plugin | Skill | 123 | 8d ago | MIT | A | 143 | Claude Code |
| design-mcp-servercyanheads/obsidian-mcp-server | Skill | 702 | 6d ago | Apache-2.0 | A | 62 | Claude Code |
| api-canvascyanheads/obsidian-mcp-server | Skill | 702 | 6d ago | Apache-2.0 | A | 85 | Claude Code |
| api-telemetrycyanheads/obsidian-mcp-server | Skill | 702 | 6d ago | Apache-2.0 | A | 85 | Claude Code |
| maintenancecyanheads/obsidian-mcp-server | Skill | 702 | 6d ago | Apache-2.0 | A | 75 | Claude Code |
| report-issue-localcyanheads/obsidian-mcp-server | Skill | 702 | 6d ago | Apache-2.0 | A | 44 | Claude Code |