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 tom5610/llm-wiki --skill lintgit clone --depth 1 https://github.com/tom5610/llm-wikiWrote 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/tom5610/llm-wiki/lint)<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>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.00059 | $0.01199 |
| Opus 5 | $0.00030 | $0.00600 |
| Sonnet 5 | $0.00012 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
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.
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.mdandwiki/log.mdexist. If either is missing, suggest running/ingeston a source first — it will bootstrap the wiki automatically.
-
Read
wiki/index.mdand scan all wiki pages inwiki/.- Scalability note: For wikis with >50 pages, use the
AskUserQuestiontool 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.
- Scalability note: For wikis with >50 pages, use the
-
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 inwiki/index.md, or index entries pointing to missing pages - Missing See also — pages lacking the mandatory
## See alsosection - Frontmatter issues — missing or malformed YAML frontmatter, wrong page type
- Misplaced files — pages in the wrong subdirectory for their
type(e.g., aconceptpage outsidewiki/concepts/) - Lens consistency — pages with a
lensfrontmatter 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 alsotechnique: what, when, how, example, pitfalls, See alsoentity: 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
- Orphan pages — pages with no inbound
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.
- 7d ago First seen · 77 lines · 59 tokens per session scan A 36f1af381a16
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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…