A command for turning raw source material into organized wiki articles. It combines information, links related topics, and structures the resulting knowledge.

Use it to create articles from collected source material and connect related facts and topics in an active wiki.

It removes the need to manually assemble scattered notes and sources into readable reference pages.

compile — 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/compile

Clone the repo

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

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

When invoked 1,841 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.00020	$0.01841
Opus 5	$0.00010	$0.00920
Sonnet 5	$0.00004	$0.00368
Haiku 4.5	$0.00002	$0.00184

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

Security

Grade A, and why

compile 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 2d 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/compile.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 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 to verify. If missing → stop with "No wiki found. Run /wiki init first."

Read the compilation protocol at skills/wiki-manager/references/compilation.md and the indexing protocol at skills/wiki-manager/references/indexing.md. Then compile raw sources into wiki articles.

Inventory awareness: compile consumes raw/ and writes wiki/; it does not compile inventory records into articles. Read inventory/_index.md only to notice active candidates, blocked source queues, or next actions that explain why sources were ingested. If compilation completes work represented by an inventory record, report the recommended record update instead of silently changing operational state.

Archive awareness: compile targets active topic wikis only by default. If the resolved --wiki <name> path is archived (wikis.json status archived or path under topics/.archive/), stop and ask the user to restore the topic or rerun with --include-archived. When --include-archived is present, compile only inside that archived topic path and keep it archived; do not use archived raw sources to update active articles.

Read the full file on GitHub · 82 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.

2d ago First seen · 82 lines · 20 tokens per session scan A 274665f94e2d

Subscribe to this mod's changes

compile is a command published in the GitHub repository nvk/llm-wiki (1,175 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,841 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.

Data and AI LLM Productivity agentic-ai agentic-skills agentic-workflow claude-code codex

compile

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Your task

What this file has done since we first saw it

Other commands, from other repositories

implement

workflow-claude-commands

weather-orchestrator

project

review

research-verify