A maintenance checker for a shared LLM wiki, meaning a knowledge base used to give language models project context. It checks whether the wiki is current, consistent, linked correctly, and complete, then fixes issues it can handle.

Use it to check index entries against project files and Git history, investigate old claims, resolve contradictions, find orphan pages, repair broken links, and report issues that need a person.

It finds stale project information, conflicting statements, missing links, and pages that nothing points to. This reduces the chance that people or language models rely on outdated wiki content.

wiki-lint — Skill for Claude Code and Codex by keysersoose

Install

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.

Any agent

npx skills add keysersoose/claude-code-setup --skill wiki-lint

Clone the repo

git clone --depth 1 https://github.com/keysersoose/claude-code-setup

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/wiki-lint/github.svg)](https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-lint)

Your own site

<a href="https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-lint"><img src="https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-lint"><img src="https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/wiki-lint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 110 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 777 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00110	$0.00777
Opus 5.5	$0.00044	$0.00311
Sonnet 5.5	$0.00022	$0.00155
Haiku 4.5	$0.00011	$0.00078

Measured 2mo ago against content hash 6aacaa7d24e8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

skills/wiki-lint/SKILL.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/wiki-lint — wiki maintenance pass

The wiki is the codebase; this is its test suite. WIKI = the global knowledge base path defined in your global CLAUDE.md. It is a git repo — every lint run ends with a commit, so damage is always recoverable.

Checks (run all, cheap subagents for the reading)

Delegate bulk reading to a cheap subagent that returns findings as a packet; verify load-bearing claims yourself before editing (leads, not facts).

Index freshness — does every status line in index.md match the current reality in its project page AND the actual repo state (git log dates, status files)? The index is the highest-traffic file; it rots first.
Stale claims — frontmatter updated: older than 30 days on an ACTIVE project's page = suspect. Cross-check the 2-3 most load-bearing claims per stale page against reality (repo, status files). Fix or mark.
Contradictions — same fact stated differently in two places (index vs page, page vs me/, wiki vs project CLAUDE.md). One fact, one place: fix the copies to reference the canonical location.
Orphans — pages nothing links to (grep for [[name]] and ](path references). Either link them from the right index/_index page or propose deletion.
Broken links — [[wikilinks]] and relative markdown links pointing at files that don't exist. Fix or remove.
Delete-when-wrong sweep — anything proven false (old model names, dead tools, superseded decisions): DELETE the claim, don't annotate around it. Update an existing page rather than creating a duplicate; delete notes that turn out to be wrong.
Log hygiene — daily logs are append-only (never rewrite), but check the last week's rich summaries exist; a run of marker-only days means the session-end summaries aren't being written — flag it.
Size guard — index.md should stay under ~60 lines of content; me/ files under ~30. If growing, tighten: statuses move to pages, index keeps one line each.

Output

Apply all safe fixes directly (index refresh, link repair, deletions of proven-wrong claims, updated: bumps).
git -C <WIKI> add -A && git commit with message lint: <date> — <n> fixes, <n> flags.
Report to the user: fixes applied, contradictions that needed judgment, anything flagged for them (risks noted in pages, decisions only they can make).
Append a one-line entry to today's log: ## [YYYY-MM-DD] lint | wiki | <n> fixes.

Read the full file on GitHub · 40 lines

Changes

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.

2mo ago First seen · 40 lines · 110 tokens per session scan A 6aacaa7d24e8

Subscribe to this mod's changes

wiki-lint is a skill published in the GitHub repository keysersoose/claude-code-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 110 tokens to every session and 777 once invoked, about $0.0004 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.

Writing and docs

wiki-lint next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wiki-lintkeysersoose/claude-code-setup	Skill	2	4mo ago	MIT	A	110	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code