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-capture)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-capture"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-capture/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-capture"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-capture.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.01224 |
| Opus 5 | $0.00000 | $0.00612 |
| Sonnet 5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
wiki-capture 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture a Link Into the Wiki
Capture a URL plus user context, normalize it into a durable markdown source, then connect it to the global wiki, local project wiki, or both.
Arguments
/wiki-capture <url>— capture a link and ask for context/wiki-capture <url> --context "why this matters"— capture with explicit context/wiki-capture <url> --no-update— only write the source markdown; do not update wiki articles
Codex prompt equivalents:
https://example.com/article
capture this in my wiki
or:
Capture this in my wiki:
{url}
Context: {why it matters to the work I am doing}
Instructions
Step 1: Resolve target wiki
Default global wiki:
~/Knowledge
Override:
LLM_WIKI_GLOBAL_DIR=/path/to/wiki-root
Routing rules:
- If the user says "my wiki", "global wiki", "personal wiki", or just "capture this in my wiki", use the global wiki by default.
- If the user says "this repo", "this project", "local wiki", or "project wiki", use the nearest local
.wiki-compiler.json. - If the user says "both", capture into both global and local wiki targets.
- If no local
.wiki-compiler.jsonexists and the user asks for local capture, offer to initialize one. - If no global
.wiki-compiler.jsonexists, initialize the global wiki automatically fromtemplates/global-wiki-config.jsonbefore capture. - If a local wiki exists and the capture defaults to global, mention that a local wiki is available and offer to also connect the source there when it clearly relates to the current project.
Step 2: Validate wiki config
- For each target wiki, read
.wiki-compiler.json. - Confirm
outputis set. - If the target wiki has not been compiled yet, still allow capture, but explain that connections will be stronger after the first compile.
Step 3: Collect user context
- If
--contextis absent, ask:"What should I pay attention to? For example: how this link relates to the product, codebase, strategy, customer, or workflow."
- Treat this context as part of the source, not as a transient instruction.
- Do not summarize the link generically. Read it through the user's context.
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 · 160 lines · 0 tokens per session scan A 474938d3ba6f
wiki-capture 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 1,224 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.