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.
git clone --depth 1 https://github.com/ussumant/llm-wiki-compilerWrote 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/commands/ussumant/llm-wiki-compiler/wiki-compile)<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>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.1 | $0.00000 | $0.00374 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
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.
What it actually says
Compile Knowledge Base Wiki
Compile all configured markdown source files into a topic-based wiki.
Instructions
-
Read configuration from
.wiki-compiler.jsonin the project root (or nearest parent directory). If not found, tell the user to run/wiki-initfirst. -
Validate configuration:
sources[]must have at least one entryoutputmust be set- Source paths must exist
-
Read schema from
{output}/schema.mdif 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. -
Invoke the
wiki-compilerskill to run the compilation:- Pass
article_sectionsfrom 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_sectionsfor 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
- Pass
-
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
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.
- 9d ago First seen · 34 lines · 0 tokens per session scan A 287a72993545
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.