A command for checking the health of a wiki, a collection of linked knowledge-base pages. It looks for broken links, missing indexes, outdated content, archive mismatches, and other consistency problems.

It is for validating wiki links and structure, detecting stale or missing pages, checking archive records, and reporting suggested improvements.

It finds issues that make a wiki harder to navigate or trust. It also checks that the wiki's stored registry and actual folders agree.

lint — Command for coding agents by nvk: A command for checking the health of a wiki…

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.

agentmods

npx agentmods add commands/nvk/llm-wiki/lint

Clone the repo

git clone --depth 1 https://github.com/nvk/llm-wiki

Or install claude-plugin, the plugin that ships this one along with the rest of its 1 skill, 28 commands.

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. Scan, not verified.

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	$0.00028	$0.03257
Opus 5	$0.00014	$0.01629
Sonnet 5	$0.00006	$0.00651
Haiku 4.5	$0.00003	$0.00326

Measured 3d ago against content hash 4aa5095bdd87, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

claude-plugin/commands/lint.md · 163 lines

How it starts

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

Your task

Resolve the wiki. Do NOT search the filesystem or read reference files — follow these steps:

Read $HOME/.config/llm-wiki/config.json. If it has hub_path, expand leading ~ only (not tildes in com~apple~CloudDocs) and prefer that path; use resolved_path only as a fallback cache when the expanded hub_path is unavailable and resolved_path is initialized. If config has only resolved_path, use it. If the configured path can be statted but reading wikis.json or listing topics/ fails with Operation not permitted, stop and ask the user to grant Full Disk Access/iCloud Drive access to the launcher; do not fall back to ~/wiki or resolved_path. Do not write machine-specific resolved_path into shared configs.
If no config → read $HOME/wiki/_index.md. If it exists → HUB = $HOME/wiki. If nothing found, ask the user where to create the wiki.
Wiki location (first match): --local → .wiki/ in CWD; --wiki <name> → HUB/wikis.json lookup with portable path resolution (<HUB>, ~, absolute, or HUB-relative); if the registry path is stale, fall back to HUB/topics/<name>; CWD has .wiki/ → use it; else → HUB.
Read <wiki>/_index.md to verify. If missing → stop with "No wiki found. Run /wiki init first."

Read the linting rules at skills/wiki-manager/references/linting.md. Then run health checks on the wiki.

Parse $ARGUMENTS

--fix: Automatically fix issues found (default: report only)
--deep: Also use WebSearch to fact-check claims and find missing information
--include-archived: Include archived topic wikis in structural maintenance. Do not create freshness chores unless the user explicitly asks for a full archived maintenance pass.
--archived-only: Check only archived topic wikis under HUB/topics/.archive/.

Run Checks

Execute checks from references/linting.md. Order matters: C13 (alias rewrite) must run before C2 and C11 so downstream checks see canonical field names, and C11 (placement) must run before C3 so the index pass sees final file locations.

Read the full file on GitHub · 163 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.

3d ago First seen · 163 lines · 28 tokens per session scan A 4aa5095bdd87

Subscribe to this mod's changes

lint is a command published in the GitHub repository nvk/llm-wiki (1,175 stars, last pushed 6d ago), licensed MIT. It adds 28 tokens to every session and 3,257 once invoked, about $0.0001 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.

LLM agentic-ai agentic-skills agentic-workflow claude-code codex

lint

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Your task

Parse $ARGUMENTS

Run Checks

What this file has done since we first saw it

Other commands, from other repositories

implement

loop

project

status

ask

test-feature