lint

A health-check command for a documentation wiki. It looks for structural problems such as broken links, missing page metadata, orphaned pages, outdated code references, and incomplete indexes.

In plain words
What is it for?
It is for checking wiki links, page structure, source records, diagrams, indexes, summaries, terminology, stale content, contradictions, and coverage.
Why use it?
It finds documentation defects that are easy to miss during normal editing. It can also apply automatic repairs according to the wiki's autonomy settings.

Command

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/narailabs/doc-wiki/lint
Clone the repo
git clone --depth 1 https://github.com/narailabs/doc-wiki
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 216 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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00216
Opus 5 $0.00003 $0.00108
Sonnet 5 $0.00001 $0.00043
Haiku 4.5 $0.00001 $0.00022

Measured 2d ago against content hash 04c6e9aa8e9c, 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 2d 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.

commands/lint.md · 12 lines

What it actually says

Invoke the doc-wiki skill to run the /doc-wiki:lint workflow with the user's arguments: $ARGUMENTS

Call Skill(doc-wiki, "lint $ARGUMENTS"). The skill orchestrator reads skills/doc-wiki/SKILL.md, locates the ### /doc-wiki:lint — Health check + auto-heal section, runs lint_checks.ts for structural issues (broken links, missing frontmatter, orphans, isolated nodes, code-ref drift, provenance completeness, Mermaid syntax, index coverage, summaries sync, ORM mapping freshness, thin clusters), then performs LLM-driven checks for factual contradictions, stale content, terminology consistency, and missing coverage. Applies auto-fixes per the configured autonomy mode.

If $ARGUMENTS is empty, default the wiki root to the current working directory.

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.

  1. 2d ago First seen · 12 lines · 6 tokens per session scan A 04c6e9aa8e9c

Subscribe to this mod's changes

lint is a command published in the GitHub repository narailabs/doc-wiki (13 stars, last pushed 3d ago), licensed Apache-2.0. It adds 6 tokens to every session and 216 once invoked, about $0.0000 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.