wiki-compile

wiki-compile is a command for Claude Code from ussumant/llm-wiki-compiler. It costs 0 tokens per session (374 once invoked), scanned A, original, MIT.

A command that turns configured Markdown source files into a topic-based wiki. It scans the sources, groups information into topics and concepts, creates articles, updates the index, and records compilation state.

In plain words
What is it for?
Use it to compile or refresh a wiki from configured source paths, apply its schema and article sections, and update the generated index and state.
Why use it?
It converts scattered documentation and notes into a consistent structure that can be searched and queried later.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the llm-wiki-compiler plugin — 1 skill, 12 commands, 1 hook shipped together

Good fit Use it to compile or refresh a wiki from configured source paths, apply its schema and article sections, and update the generated index and state.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/ussumant/llm-wiki-compiler/wiki-compile
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.

Clone the repo
git clone --depth 1 https://github.com/ussumant/llm-wiki-compiler

Made for: Claude Code.

Or install llm-wiki-compiler, the plugin that ships this one along with the rest of its 1 skill, 12 commands, 1 hook.

Wrote 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.

agentmods badge for wiki-compile

README.md
[![agentmods](https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-compile.svg)](https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-compile)
Your own site
<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-compile"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-compile.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 374 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00374
Opus 5 $0.00000 $0.00187
Sonnet 5 $0.00000 $0.00075
Haiku 4.5 $0.00000 $0.00037

Measured 9d ago against content hash 287a72993545, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

wiki-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 9d 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.

plugin/commands/wiki-compile.md · 34 lines

What it actually says

Compile Knowledge Base Wiki

Compile all configured markdown source files into a topic-based wiki.

Instructions

  1. Read configuration from .wiki-compiler.json in the project root (or nearest parent directory). If not found, tell the user to run /wiki-init first.

  2. Validate configuration:

    • sources[] must have at least one entry
    • output must be set
    • Source paths must exist
  3. Read schema from {output}/schema.md if it exists. Use it to guide topic/concept classification and naming. If it doesn't exist (first run), it will be generated in Phase 3.7.

  4. Invoke the wiki-compiler skill to run the compilation:

    • Pass article_sections from config to the skill (if present — legacy configs may not have this field)
    • Phase 1: Scan sources
    • Phase 2: Classify and discover topics (respecting schema if present)
    • Phase 3: Compile topic articles using article_sections for structure (use parallel agents when possible)
    • Phase 3.5: Discover and compile concept articles (cross-cutting patterns)
    • Phase 3.7: Generate or update schema.md
    • Phase 4: Update INDEX.md (now includes concepts section)
    • Phase 5: Update state and log
  5. Show completion summary with topics created/updated, concepts discovered, source count, and schema changes.

Arguments

  • No arguments: incremental compilation (recompile changed topics)
  • --full: force recompile all topics regardless of changes
  • --topic {slug}: recompile only the specified topic
  • --dry-run: show what would be compiled without writing files
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.

  1. 9d ago First seen · 34 lines · 0 tokens per session scan A 287a72993545

Subscribe to this mod's changes

wiki-compile is a command published in the GitHub repository ussumant/llm-wiki-compiler (321 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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.