lint

lint is a skill for Claude Code from tom5610/llm-wiki. It costs 59 tokens per session (1,199 once invoked), scanned A, original, MIT.

A health check for a markdown wiki, a collection of linked documentation pages. It looks for broken or missing links, contradictions, outdated claims, orphan pages, and content gaps, then groups findings by severity.

In plain words
What is it for?
Auditing a wiki, checking recent changes, finding pages missing from its index, and identifying claims or cross-references that need attention.
Why use it?
It helps maintainers find documentation problems that make information hard to navigate or trust.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the llm-wiki plugin — 5 skills, 1 hook shipped together

Good fit Auditing a wiki, checking recent changes, finding pages missing from its index, and identifying claims or cross-references that need attention.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tom5610/llm-wiki/lint
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 tom5610/llm-wiki --skill lint
Clone the repo
git clone --depth 1 https://github.com/tom5610/llm-wiki

Made for: Claude Code.

Or install llm-wiki, the plugin that ships this one along with the rest of its 5 skills, 1 hook.

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.

agentmods badge for lint

README.md
[![agentmods](https://agentmods.dev/badge/skills/tom5610/llm-wiki/lint.svg)](https://agentmods.dev/skills/tom5610/llm-wiki/lint)
Your own site
<a href="https://agentmods.dev/skills/tom5610/llm-wiki/lint"><img src="https://agentmods.dev/badge/skills/tom5610/llm-wiki/lint.svg" alt="Measured on agentmods" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,199 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01199
Opus 5 $0.00030 $0.00600
Sonnet 5 $0.00012 $0.00240
Haiku 4.5 $0.00006 $0.00120

Measured 7d ago against content hash 36f1af381a16, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, 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 7d 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/lint/SKILL.md · 77 lines

How it starts

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

Lint workflow

Prerequisites

  • Verify wiki/index.md and wiki/log.md exist. If either is missing, suggest running /ingest on a source first — it will bootstrap the wiki automatically.
  1. Read wiki/index.md and scan all wiki pages in wiki/.

    • Scalability note: For wikis with >50 pages, use the AskUserQuestion tool to offer scoped lint instead of scanning everything. Options: "Full wiki lint", "By subdirectory", "By lens", "Recent changes only". Include descriptions explaining the trade-off (thoroughness vs. speed). For full-wiki lints at scale, process one subdirectory at a time and report incrementally.
    • Lens awareness: Read .llm-wiki/lenses/ to load active lens definitions. These are needed for lens-specific quality validation in content checks.
  2. Run checks across four categories:

    Structural checks

    • Orphan pages — pages with no inbound [[wikilinks]] from other pages
    • Broken links[[wikilinks]] pointing to pages that don't exist
    • Index gaps — pages in wiki/ not listed in wiki/index.md, or index entries pointing to missing pages
    • Missing See also — pages lacking the mandatory ## See also section
    • Frontmatter issues — missing or malformed YAML frontmatter, wrong page type
    • Misplaced files — pages in the wrong subdirectory for their type (e.g., a concept page outside wiki/concepts/)
    • Lens consistency — pages with a lens frontmatter field that references a non-existent or archived lens file in .llm-wiki/lenses/
    • Lens-specific type placement — pages with lens-defined custom types that are not in the correct subdirectory as specified by the lens

    Content checks

    • Contradictions — conflicting claims across pages (flag with specific quotes from both pages)
    • Stale content — claims that newer sources have superseded
    • Thin pages — pages missing required sections for their type:
      • concept: definition, principles, implications, relationships, See also
      • technique: what, when, how, example, pitfalls, See also
      • entity: background, key contributions, works, See also
      • For lens-tagged pages: also validate against the lens's "Quality Standards" section (additional required sections/fields)
    • Incomplete pages — pages with content that could be expanded from existing sources

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

  1. 7d ago First seen · 77 lines · 59 tokens per session scan A 36f1af381a16

Subscribe to this mod's changes

lint is a skill published in the GitHub repository tom5610/llm-wiki (2 stars, last pushed 4mo ago), licensed MIT. It adds 59 tokens to every session and 1,199 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens