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.
npx skills add po4yka/llm-wiki-skills --skill wiki-lintgit clone --depth 1 https://github.com/po4yka/llm-wiki-skillsWrote 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/skills/po4yka/llm-wiki-skills/wiki-lint)<a href="https://agentmods.dev/skills/po4yka/llm-wiki-skills/wiki-lint"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/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/skills/po4yka/llm-wiki-skills/wiki-lint"><img src="https://agentmods.dev/badge/skills/po4yka/llm-wiki-skills/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.00047 | $0.01107 |
| Opus 5.5 | $0.00019 | $0.00443 |
| Sonnet 5.5 | $0.00009 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00111 |
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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Lint
Goal
Detect structural decay, provenance gaps, stale claims and contradictions without silently rewriting truth.
When to use
- The vault needs a structural or trust health check.
- Before large refactors or after bulk ingestion.
- A review queue should be generated from mechanical findings.
A filled final report ships in assets/worked-example.md.
Inputs
wiki/index.mdwiki/log.md- all
wiki/**/*.mdpages _meta/taxonomy.md_meta/schemas/*- optional git history
Write permissions
Allowed:
- create reports under
_agent/reports/; - append to
wiki/log.mdwhen a report is created; - propose patches;
- fix trivial broken links only when the user explicitly asks for apply mode.
Not allowed by default:
- resolve contradictions;
- rewrite synthesis pages;
- mark pages verified;
- delete pages;
- bulk-normalize frontmatter without a dry run.
Procedure
1. Run deterministic checks
node scripts/wiki-lint-core.mjs <vault-path>
The bundled script is read-only and prints a draft report covering the mechanical checks. Do not re-derive these by hand; re-run the script instead:
- inventory: page counts by type/status, missing or malformed required frontmatter;
- links: broken wikilinks and relative links, orphan pages, pages with no outbound links, duplicate titles, near-duplicate slugs;
- provenance: generated or
reviewed/verifiedfactual pages withoutsource_paths/source_urls, high-confidence pages with no source reference; - trust:
ai_confidence < 0.70withoutreview_required: true,review_required: falseon draft pages,verifiedpages paststale_after, ambiguous claim support outside review; - taxonomy: unknown types/statuses, tags missing from
_meta/taxonomy.md, unused taxonomy tags.
Use --strict in CI to fail on critical/high findings.
2. Add judgement-only checks
The script cannot see these; check them manually:
- pages changed since the last lint and pages without source backlinks in git history;
- protected human sections changed by recent agent commits;
- stale source hashes when available;
- generated pages that cite only other generated pages;
- pages missing from
wiki/index.mdthat are likely important; - spelling-variant and overbroad tags beyond exact taxonomy mismatches.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 139 lines · 47 tokens per session scan A dc87f7cc2c17
wiki-lint is a skill published in the GitHub repository po4yka/llm-wiki-skills (4 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 1,107 once invoked, about $0.0002 per session on Opus 5.5. 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-31.
Other skills, from other repositories
obsidian-memory
Explicit-only Obsidian memory workflow. Use when the user explicitly asks to work with an Obsidian vault, LLM wiki, agent memory, RAW/source ingest, provenance, QUERY, LINT, or release safety for a markdown knowledge system. Do not auto-route ordinary coding sessions into external vault workflows.
wiki-lint
Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…
save
File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…
librarian
Orchestrate vault knowledge workflows using the Librarian MCP server. Ingest solutions, search prior art, explore the knowledge graph, log daily learnings.
wiki-export
Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…
wiki-query
Answer a question using ONLY the existing wiki vault as the knowledge base — no web search, no general LLM knowledge. Reads hot.md first (cheap recent context), then catalog.md to navigate, then drills into specific pages, then optionally semantic-searches the wiki, and synthesizes an answer with citations. Use when…