Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ussumant/llm-wiki-compiler/plugin install 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-ingest)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-ingest"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-ingest/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-ingest"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-ingest.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.00798 |
| Opus 5 | $0.00000 | $0.00399 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
wiki-ingest 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ingest a Single Source
Interactive workflow for adding one source file to the wiki. The LLM reads the file, discusses key takeaways with the user, then updates relevant topic articles.
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 one argument: the file path to ingest (e.g.,
/wiki-ingest Knowledge/meetings/2026-04-07-standup.md) - If no argument provided, ask: "Which file would you like to ingest?"
- Verify the file exists and is a
.mdfile - Check that the file is within one of the configured
sources[]directories (warn if not, but allow it)
Step 2: Read and discuss
- Read the full source file
- Present a brief summary of key takeaways (3-5 bullet points)
- Ask the user: "Anything you want me to emphasize or de-emphasize when updating the wiki?"
- Wait for the user's response before proceeding — this is the interactive part where the user guides what matters
Step 3: Classify
- Read
{output}/schema.mdto understand existing topics and naming conventions - Determine which existing topics this source belongs to (can be multiple)
- If the source introduces a genuinely new topic not in the schema, propose creating it
- Show the user: "This file touches these topics: [list]. I'll update each one. Sound right?"
- Wait for confirmation before proceeding
Step 4: Update topic articles
For each affected topic:
- Read the current topic article from
{output}/topics/{slug}.md - Read
article_sectionsfrom.wiki-compiler.json(or use default template from${CLAUDE_PLUGIN_ROOT}/templates/article-template.mdif absent) - Integrate the new source's information into the relevant sections
- Respect the user's emphasis guidance from Step 2
- Update coverage indicators — the source count may change the coverage level for some sections
- Add the new source to the Sources section (using configured
link_style) - Update the
source_countin the article frontmatter - Write the updated article
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 · 80 lines · 0 tokens per session scan A 336170ecb3f2
wiki-ingest 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 798 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.