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.
npx agentmods add commands/ussumant/llm-wiki-compiler/wiki-initgit 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-init)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-init"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-init.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.03095 |
| Opus 5 | $0.00000 | $0.01548 |
| Sonnet 5 | $0.00000 | $0.00619 |
| Haiku 4.5 | $0.00000 | $0.00310 |
Grade A, and why
wiki-init 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Knowledge Base Wiki
Interactive, conversational setup for a new knowledge base wiki. One question at a time, multiple choice when possible.
Arguments:
- (none) — auto-detects whether this is a codebase or knowledge project (see Auto-Detection below)
--codebase— force codebase mode (skip auto-detection)--knowledge— force knowledge mode (skip auto-detection)
Instructions
Important: Ask ONE question per message. Wait for the user's response before moving to the next question. Never batch multiple questions. Keep the tone conversational — like a knowledgeable colleague setting things up for you.
Auto-Detection (when no flag is provided)
Before asking any questions, scan the project root to determine the mode:
- Check for code manifest files:
package.json,go.mod,Cargo.toml,pyproject.toml,requirements.txt,Gemfile,*.sln,Package.swift,pom.xml,build.gradle - Check for markdown-heavy directories:
Knowledge/,docs/,notes/,content/,meetings/,research/, or any directory with 10+.mdfiles
Decision logic:
- Manifest found, no markdown directories → codebase mode
- Markdown directories found, no manifest → knowledge mode
- Both found → ask the user:
I see both code files and markdown knowledge directories here. A) Codebase wiki — compile a wiki about this codebase's architecture, decisions, and patterns B) Knowledge wiki — compile a wiki from your markdown files (meetings, notes, research) - Neither found → ask the user what they want to compile
Then proceed to the appropriate mode below.
Codebase Mode (--codebase or auto-detected)
When codebase mode is selected, use this streamlined flow instead of the standard 10-step process.
Codebase Step 1: Check for existing config
Same as standard Step 1 — check for .wiki-compiler.json and ask to reconfigure or abort.
Codebase Step 2: Auto-detect everything
Scan the project root and build a complete picture in one pass:
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.
- 6d ago First seen · 348 lines · 0 tokens per session scan A 3481ffcba8db
wiki-init is a command published in the GitHub repository ussumant/llm-wiki-compiler (321 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,095 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
brand-generate
Generate an on-brand document from a saved Brand Profile.
cti-report
Render case deliverables — relationship graph (PNG/SVG/Mermaid) and a polished PDF/DOCX assessment. Usage: /cti-report [--graph|--pdf].
prose-review-docs
Reviews markdown documentation files or directories against the active prose style rules — the plugin's vendor-neutral baseline plus your organization's overlay when one is configured. Accepts a file path or directory (recursive). Runs prose-style-checker and optionally Vale. Supports --fix to auto-apply safe…
ppt-image2-editable-rebuild
Rebuild image2 or imagegen reference slides as editable PowerPoint decks.
convert
Convert a file to Markdown using markitdown.
render-figures
Compile all .tex and .typ figure files in a directory.