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 skills/oshayr/llm-wiki/viewnpx skills add Oshayr/LLM-Wiki --skill viewgit 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/view)<a href="https://agentmods.dev/skills/oshayr/llm-wiki/view"><img src="https://agentmods.dev/badge/skills/oshayr/llm-wiki/view.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.00052 | $0.00566 |
| Opus 5 | $0.00026 | $0.00283 |
| Sonnet 5 | $0.00010 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
wiki-view 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.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki View
Dashboard, graph visualization, stats, and export for the wiki.
Resolve .wiki/ from plugin install scope. If not found, say "No wiki found."
Arguments
/wiki-view— dashboard summary (page count, recent activity, top topics)/wiki-view pages— list all pages grouped by type/wiki-view stats— detailed statistics (page count, links, confidence distribution, stale %)/wiki-view graph— knowledge graph visualization (Mermaid diagram)/wiki-view graph <slug>— graph centered on a specific page (2-hop neighborhood)/wiki-view export html— export entire wiki as single HTML file/wiki-view export md— export as single markdown bundle/wiki-view export json— export as JSON knowledge graph (nodes + edges)/wiki-view artifacts <type>— generate study guide, timeline, glossary, or comparison table
Dashboard
Read .wiki/index.md, .wiki/log.md, .wiki/overview.md:
- Page count and breakdown by type
- Last 5 activity log entries
- Current open questions from overview.md
- Confidence distribution (high/medium/low)
Graph
Read all pages, extract [[wiki-links]] and related: fields:
- Generate Mermaid flowchart showing page connections
- Color by type (concept=blue, entity=green, source=gray, idea=yellow)
- Highlight orphans (no incoming links) in red
- For
--slug: show only 2-hop neighborhood of that page
Export
- HTML: Render all pages through markdown → styled single HTML document
- Markdown: Concatenate all pages with
---separators - JSON:
{"nodes": [...], "edges": [...]}knowledge graph format
Artifacts
Generate derivative documents from wiki content:
/wiki-view artifacts study-guide <topic>— structured study guide from topic cluster/wiki-view artifacts timeline <topic>— chronological timeline of events/developments/wiki-view artifacts glossary— terms and definitions from all pages/wiki-view artifacts compare <slug1> <slug2>— side-by-side comparison table
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 · 53 lines · 52 tokens per session scan A a8e6bcbb3fb9
wiki-view is a skill published in the GitHub repository Oshayr/LLM-Wiki (49 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 566 once invoked, about $0.0003 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 skills, from other repositories
llm-wiki
Build and maintain an LLM-curated personal knowledge base — the "LLM Wiki" pattern from Andrej Karpathy's April 2026 gist. Use this skill whenever the user wants to ingest a source (paper, article, transcript, PDF, notes) into a persistent compounding knowledge base, ask a question against accumulated notes, lint or…
research-wiki
Persistent research knowledge base that accumulates papers, ideas, experiments, claims, and their relationships across the entire research lifecycle. Inspired by Karpathy's LLM Wiki pattern. Use when user says "知识库", "research wiki", "add paper", "wiki query", "查知识库", or wants to build/query a persistent field map.
alive:save
The human wants to checkpoint. Or: the stash has grown heavy — 5+ items, 30+ minutes, a natural pause in the work. The squirrel doesn't decide when to save. It surfaces the need and lets the human pull the trigger. Runs the full save protocol: confirms stash, writes log, updates state, generates projections…
alive:capture-context
Use when external content arrives in the session — emails, transcripts, screenshots, documents, files, or in-session research worth keeping. Also use when there's nothing obvious to capture — the skill checks 03Inbox/ for unrouted files and enters inbox scan mode. Stores raw content, routes to bundles, extracts tasks…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:load-context
The human mentions a walnut to work on, asks about a specific venture/experiment/project, or wants to check status — not just explicit 'load X'. Load the brief pack (3 files), resolve the people involved, check the active bundle — then surface one observation and ask what to work on. Context loads in tiers: walnut and…