A command for working with an llm-wiki knowledge base, a collection of local notes and reference material that an agent can query and update.

Use it to ask questions, research, audit, resume work, add URLs, collect catalogues, track inventory, manage ideas, or edit connected resources.

It gives one route for common wiki tasks instead of requiring you to manage the underlying files yourself.

wiki — Command by nvk

Install

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.

agentmods

npx agentmods add commands/nvk/llm-wiki/wiki

Clone the repo

git clone --depth 1 https://github.com/nvk/llm-wiki

Per session 76 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 6,629 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00076	$0.06629
Opus 5	$0.00038	$0.03315
Sonnet 5	$0.00015	$0.01326
Haiku 4.5	$0.00008	$0.00663

Measured 3d ago against content hash 2b7f031c1945, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

claude-plugin/commands/wiki.md · 364 lines

How it starts

The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Your task

Resolve the wiki. Do NOT search the filesystem or read reference files — follow these steps:

Read $HOME/.config/llm-wiki/config.json. If it has hub_path, expand leading ~ only (not tildes in com~apple~CloudDocs) and prefer that path; use resolved_path only as a fallback cache when the expanded hub_path is unavailable and resolved_path is initialized. If config has only resolved_path, use it. If the configured path can be statted but reading wikis.json or listing topics/ fails with Operation not permitted, stop and ask the user to grant Full Disk Access/iCloud Drive access to the launcher; do not fall back to ~/wiki or resolved_path. Do not write machine-specific resolved_path into shared configs.
If no config → read $HOME/wiki/_index.md. If it exists → HUB = $HOME/wiki. If nothing found, ask the user where to create the wiki.
Wiki location (first match): --local → .wiki/ in CWD; --wiki <name> → HUB/wikis.json lookup with portable path resolution (<HUB>, ~, absolute, or HUB-relative); if the registry path is stale, fall back to HUB/topics/<name>; CWD has .wiki/ → use it; else → HUB.
Read <wiki>/_index.md if found. Variant: wiki-neutral — wiki.md is the router, init, and config command, so "wiki missing" is not always an error; the init subcommand creates the wiki, status shows an empty hub gracefully, and the natural-language router explains how to create one.

You are the llm-wiki knowledge base manager. Read the skill at skills/wiki-manager/SKILL.md and structure reference at skills/wiki-manager/references/wiki-structure.md for full conventions.

If $ARGUMENTS contains "init"

Initialize a new wiki. Parse arguments:

init <name> → create topic wiki at HUB/topics/<name>/
init <name> --local → create local wiki at .wiki/ in current project
init (no name) → ask: "What topic is this for?" Then create the topic wiki with their answer.

A topic name is always required. There is no bare global wiki — HUB is only a hub (wikis.json + _index.md + log.md). All content lives in topic sub-wikis.

Read the full file on GitHub · 364 lines

Changes

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.

3d ago First seen · 364 lines · 76 tokens per session scan A 2b7f031c1945

Subscribe to this mod's changes

wiki is a command published in the GitHub repository nvk/llm-wiki (1,175 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 6,629 once invoked, about $0.0004 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.

LLM Memory and context agentic-ai agentic-skills agentic-workflow claude-code codex

wiki

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Your task

If $ARGUMENTS contains "init"

What this file has done since we first saw it

Other commands, from other repositories

implement

loop

project

review

status

story-implement-auto