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-search)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-search"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-search/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.
<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-search"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-search.svg" alt="Reviewed on agentmods" width="80" 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.00558 |
| Opus 5 | $0.00000 | $0.00279 |
| Sonnet 5 | $0.00000 | $0.00112 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
wiki-search 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search the Wiki
Search across all wiki articles for keywords, phrases, or topics.
Instructions
Step 1: Validate
- Read
.wiki-compiler.jsonfrom the project root (or nearest parent directory). If not found, tell the user to run/wiki-initfirst. - Accept a search query as argument (e.g.,
/wiki-search retention experiments) - If no argument provided, ask: "What are you looking for?"
Step 2: Search strategy
Use a two-tier search approach:
Tier 1 — Index scan (fast, try this first):
- Read
{output}/INDEX.md - Check topic names and one-line summaries for keyword matches
- This is usually sufficient for "which topic covers X?" questions
Tier 2 — Full article search (when Tier 1 isn't enough):
- Use Grep to search across all files in
{output}/topics/and{output}/concepts/for the search terms - Return matching sections with context — include the section heading (
##) and surrounding lines so the user can see the match in context - Search both topic articles and concept articles
Step 3: Present results
Format results clearly:
Found {N} matches for "{query}":
### Topics
- **{topic-name}** [coverage: {level}] — {matching excerpt}
→ {output}/topics/{slug}.md
### Concepts
- **{concept-name}** — {matching excerpt}
→ {output}/concepts/{slug}.md
Include coverage indicators so the user knows whether to trust the wiki excerpt or read raw sources.
If no matches found:
- Suggest related topics that might be relevant
- Recommend
/wiki-queryfor synthesis questions that require connecting multiple topics - Suggest
/wiki-ingestif the user thinks the knowledge should be in the wiki but isn't
Step 4: Offer next steps
Based on results:
- "Want me to read the full article on {topic}?"
- "Want to ask a deeper question? Try
/wiki-query {your question}" - If search reveals a gap: "This area has low coverage. Want to
/wiki-ingesta source to improve it?"
Arguments
- Search query as argument (can be multiple words)
- No arguments: prompts user to specify what they're looking for
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.
- 10d ago First seen · 65 lines · 0 tokens per session scan A 92ec6fb62ea1
wiki-search is a command published in the GitHub repository ussumant/llm-wiki-compiler (321 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 558 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.