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-lint)<a href="https://agentmods.dev/commands/ussumant/llm-wiki-compiler/wiki-lint"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-lint/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-lint"><img src="https://agentmods.dev/badge/commands/ussumant/llm-wiki-compiler/wiki-lint.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.00668 |
| Opus 5 | $0.00000 | $0.00334 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
wiki-lint 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint Knowledge Base Wiki
Run health checks on the compiled wiki to find issues.
Instructions
-
Read configuration from
.wiki-compiler.json. If not found, tell the user to run/wiki-initfirst. -
Read the wiki state:
- Read
{output}/INDEX.mdfor current topics - Read
{output}/schema.mdfor expected structure (if exists) - Read
{output}/.compile-state.jsonfor last compilation state
- Read
-
Run these checks:
Check 1: Stale Articles
Compare source file modification dates against .compile-state.json. Flag topics whose sources have changed since last compile.
Check 2: Orphan Pages
Check each wiki article's Sources section. Flag articles where:
- Source files no longer exist (were deleted or moved)
- Article has 0 sources listed
Check 3: Missing Cross-References
For each pair of topics, count shared sources. If two topics share 3+ sources but neither references the other, suggest a cross-reference.
Check 4: Low Coverage Sections
Scan all articles for [coverage: low] tags. List them as improvement candidates -- these sections should either be expanded with more sources or flagged as known gaps.
Check 5: Contradictions
Compare key facts across articles. Look for:
- Different dates for the same event in different articles
- Conflicting metrics (e.g., "D1 is 17.5%" in one article, "D1 is 13.3%" in another)
- Decisions described differently across topics
Check 6: Schema Drift
If schema.md exists:
- Topics in
topics/directory not listed in schema.md - Topics listed in schema.md that don't have a corresponding article
- Article sections that don't match the schema's Article Structure
- Output a summary:
Wiki Lint: "{name}"
──────────────────────────
Stale: {N} topics (sources changed since last compile)
Orphans: {N} articles with missing sources
Cross-refs: {N} missing links suggested
Low coverage: {N} sections across {N} topics
Contradictions: {N} found
Schema drift: {N} mismatches
{Details for each finding, grouped by check}
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 · 69 lines · 0 tokens per session scan A 8dbb1c5c67a7
wiki-lint 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 668 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.