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 vanillaflava/llm-wiki-skills --skill wiki-lintgit clone --depth 1 https://github.com/vanillaflava/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/vanillaflava/llm-wiki-skills/wiki-lint)<a href="https://agentmods.dev/skills/vanillaflava/llm-wiki-skills/wiki-lint"><img src="https://agentmods.dev/badge/skills/vanillaflava/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/vanillaflava/llm-wiki-skills/wiki-lint"><img src="https://agentmods.dev/badge/skills/vanillaflava/llm-wiki-skills/wiki-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00177 | $0.04636 |
| Opus 5 | $0.00088 | $0.02318 |
| Sonnet 5 | $0.00035 | $0.00927 |
| Haiku 4.5 | $0.00018 | $0.00464 |
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 12d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Lint
Health-checks the wiki and produces a report. Never modifies wiki content.
Config Discovery
Every invocation starts here. Wiki root is the directory containing wiki-config.md. Skills derive it at runtime. Pages this skill lints are checked against the structure in wiki-schema.md - both files need to be present.
-
Identify scope: Determine your filesystem scope root - the top-level directory your filesystem tool can access.
-
Scope check - MANDATORY STOP: If scope is bare drive root (
C:\,D:\,/), OS root, or user home (C:\Users\X,/home/X,/Users/X) → stop immediately. Do not search. Do not attempt to locate wiki-config.md. Go directly to step 6. -
Scan
<available_skills>forwiki-config. Note whether it's available - this shapes the recommendations below. The bundledreferences/setup-help.mdis also available; read it if the user needs orientation or if you get stuck. -
Locate and read
wiki-config.md: Search recursively (first-match, max 5 levels). If found, read it (blacklist,index_excludes,ingested_folder,ingested_subdirs,log_format). If not found, skip to step 6. -
Locate and read
wiki-schema.md- mandatory check: In the same directory aswiki-config.md, verifywiki-schema.mdexists and parses as YAML. Do not proceed to the Workflow below until you have a definite verdict (present / missing / malformed). Then:-
Present and parses cleanly → read the schema (
mandatory_fields,conditional_fields,enums) and proceed to the Workflow. -
Missing → STOP. Do not proceed. Do not deploy. Response depends on whether
wiki-configis in<available_skills>(from step 3):- wiki-config available: Output exactly this pattern - "Your wiki is missing
wiki-schema.md. Run/wiki-configto deploy it and complete setup. I'll wait for that to be done before proceeding." End of turn. Do not offer bundled deployment; do not present alternatives. wiki-config's guided flow is the correct path when wiki-config is available.
- wiki-config available: Output exactly this pattern - "Your wiki is missing
-
What ships with it
3 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.
- 12d ago First seen · 285 lines · 177 tokens per session scan A b22264bd600e
wiki-lint is a skill published in the GitHub repository vanillaflava/llm-wiki-skills (64 stars, last pushed 2mo ago), licensed MIT. It adds 177 tokens to every session and 4,636 once invoked, about $0.0009 per session on Opus 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-30.
Other skills, from other repositories
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
mindbase
Maintain a persistent AI-tended research wiki. Activates when the user wants to ingest a source (PDF, URL, article, paste), capture a thought, build the wiki context, query what's already known, lint for orphans/contradictions, or maintain page conventions. Phrases include "add this to my wiki", "today I decided…"…
llm-wiki-pm
Persistent PM knowledge base, competitive intel, customer notes, strategy, roadmap, AI market. Markdown wiki with entities, concepts, comparisons. Ingest sources, query, update with diffs, lint. Fires on "remember that / note that / don't forget / what do we know about X / what am I missing / blind spots".
llm-wiki-brief
Structured daily/weekly briefs, tag digests, and check-ins from the PM wiki. Richer output than core catch-me-up.
llm-wiki-crm
PM relationship CRM layer on top of the wiki. Relationship health, auto-enrichment via web search, account health tracking, and people profile maintenance. Does not replace Salesforce — tracks PM-specific context (product feedback, feature asks, strategic relationship, communication history).
llm-wiki-research
Research sprints, competitive deep dives, and auto-enrichment of stub wiki pages. Delegates web fetching to worker-source-fetcher. Files all findings back into the wiki.