wiki-migrate

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

A one-time command that examines the files read when an agent session starts and shows which of those reads could be replaced by wiki articles. A wiki is a collection of linked documentation pages organized for reference.

In plain words
What is it for?
Use it to compare AGENTS.md or CLAUDE.md startup instructions with the compiled wiki index and topics. It helps map startup files to the wiki articles that cover them.
Why use it?
It can reduce repeated loading of raw files at the start of each session by identifying information already covered in the wiki. It also checks that the wiki has been initialized and compiled before making suggestions.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

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

Good fit Use it to compare AGENTS.md or CLAUDE.md startup instructions with the compiled wiki index and topics. It helps map startup files to the wiki articles that cover them.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-migrate/github.svg)](https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-migrate)
Your own site
<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-migrate"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-migrate/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.

agentmods 80×15 button for wiki-migrate

Your own site · 80×15
<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-migrate"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-migrate.svg" alt="Reviewed on agentmods" width="80" 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 738 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.00738
Opus 5 $0.00000 $0.00369
Sonnet 5 $0.00000 $0.00148
Haiku 4.5 $0.00000 $0.00074

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

Security

Grade A, and why

wiki-migrate 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-migrate.md · 88 lines

How it starts

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

Migrate to Wiki-First Startup

One-time migration command. Analyzes your AGENTS.md or CLAUDE.md session startup sequence and shows which raw file reads can be replaced by wiki articles.

Instructions

Step 1: Validate

  • Read .wiki-compiler.json — if not found, tell the user to run /wiki-init first
  • Check that the wiki has been compiled at least once (INDEX.md and topic articles exist)
  • If not compiled, tell the user to run /wiki-compile first

Step 2: Find startup instructions

Look for session startup instructions in this order:

  1. AGENTS.md in the project root
  2. CLAUDE.md in the project root
  3. Any file referenced by CLAUDE.md that contains startup/context loading instructions

Identify the section that lists files to read at session start. Look for patterns like:

  • "Read these files", "Session Startup", "Before doing any work, read..."
  • Numbered lists of file paths with descriptions
  • References to context files, knowledge bases, or startup sequences

Step 3: Map raw files to wiki topics

For each file listed in the startup sequence:

  1. Read the wiki INDEX.md to get the list of topics
  2. For each raw file, check if its content is covered by a wiki topic:
    • Match by filename appearing in a topic's Sources section
    • Match by content overlap (the raw file's key terms appearing in a topic article)
  3. Check the coverage level of the relevant topic sections

Step 4: Present the coverage report

Wiki Migration Report for {project name}

Current startup: {N} file reads

✅ {filename} → covered by {topic} [coverage: high]
✅ {filename} → covered by {topic} [coverage: high]
⚠️ {filename} → partially covered by {topic} [coverage: medium]
   → Check raw source for: {what's missing}
⚠️ {filename} → partially covered by {topic} [coverage: low]
   → Read raw source directly for granular detail
❌ {filename} → not covered by any wiki topic
   → Keep this in startup, or /wiki-ingest to add it

Summary: {covered}/{total} reads can be replaced by wiki
Estimated token savings: ~{old_tokens} → ~{new_tokens} ({reduction}% reduction)

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

  1. 9d ago First seen · 88 lines · 0 tokens per session scan A 6bcc73c7adbf

Subscribe to this mod's changes

wiki-migrate 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 738 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.