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-query)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-query"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-query/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-query"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-query.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.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
wiki-query 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
Query Knowledge Base Wiki
Search the compiled wiki to answer a question. Faster and cheaper than reading raw source files.
Arguments
The user's question is passed as $ARGUMENTS. Example: /wiki-query what do we know about retention?
Instructions
-
Read configuration from
.wiki-compiler.json. If not found, tell user to run/wiki-init. -
Read INDEX.md from the configured output directory to see all available topics.
-
Read schema.md if it exists -- check for cross-reference rules that might point to related topics.
-
Identify relevant topics -- based on the user's question, select 1-3 topic articles most likely to contain the answer.
-
Read the selected topic articles from
{output}/topics/. -
Answer the question with:
- Specific facts, dates, and decisions from the wiki articles
- Citations in the format:
(from: {topic name} > {section}) - If the wiki doesn't have enough detail, point the user to specific raw source files from the article's Sources section
-
Keep it concise -- the user wants an answer, not a summary of every article you read.
-
Offer to file the answer -- if the answer synthesizes information in a useful way that isn't already in a wiki article, ask:
"This answer connects information across topics. Want me to file it into the wiki? (y/n)"
If yes:
- Append the synthesis to the most relevant topic article (add a new subsection or expand an existing section)
- Add a note:
*Filed from query on {date}* - Log it in
{output}/log.md:### {date} -- Query Filed - Question: "{question}" - Filed to: {topic-slug} > {section}
If the answer doesn't add new synthesis (just restated what's already in the article), skip the filing offer.
If no wiki exists
If INDEX.md doesn't exist or the wiki hasn't been compiled yet:
Wiki not compiled yet. Run /wiki-compile first, then try your query again.
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 · 50 lines · 0 tokens per session scan A 0bc5a0962086
wiki-query 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 462 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.