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 shrimbly/project-wiki --skill wiki-lintgit clone --depth 1 https://github.com/shrimbly/project-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/shrimbly/project-wiki/wiki-lint)<a href="https://agentmods.dev/skills/shrimbly/project-wiki/wiki-lint"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/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.
<a href="https://agentmods.dev/skills/shrimbly/project-wiki/wiki-lint"><img src="https://agentmods.dev/badge/skills/shrimbly/project-wiki/wiki-lint.svg" alt="Reviewed on agentmods" width="80" 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.00081 | $0.00653 |
| Opus 5 | $0.00041 | $0.00327 |
| Sonnet 5 | $0.00016 | $0.00131 |
| Haiku 4.5 | $0.00008 | $0.00065 |
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 10d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wiki-lint
Audit the wiki for drift and inconsistency. Read CLAUDE.md for the conventions
you're checking against.
What to check
Walk wiki/ (and cross-reference sources/) for:
- Contradictions — two pages asserting incompatible things. The most important class; surface every one.
- Stale claims — a wiki claim a newer source has superseded. Check
fetcheddates and decision supersession chains. - Orphan pages — a wiki page with no inbound links from any other page or the index. Either link it in or question whether it should exist.
- Missing pages — a concept/entity referenced repeatedly across sources or wiki pages but with no page of its own.
- Missing cross-references — pages that clearly relate but don't link each
other (check
related:both directions). - Uncited claims — wiki assertions with no
sources:backing. Either find the source or flag the claim as unsupported. - Dangling links — viewer URLs (
/wiki-...-x/,/<source>/) pointing at pages/sources that don't exist. - Resolved-but-open — entries in
wiki/open-questions.mdthat other pages have since answered. - Index drift — pages missing from
wiki/index.md, or index entries for pages that no longer exist. - Stale annotations —
annotations/*.jsonwhosequoteno longer matches the underlying doc (the viewer shows these as orphaned); note any unaddressed user comments.
How to run it
- Let the user scope it if they want ("just the entities", "everything"); default to a full pass.
- Fix the safe, unambiguous issues directly: add a missing cross-link, correct
a dangling URL, move a resolved question, add a missing index entry, add a
missing
sources:reference you can verify. - Don't silently resolve judgment calls: for contradictions and stale-vs-current
ambiguities, present the conflict and the evidence and let the user decide (or
open an entry in
wiki/open-questions.md).
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.
- 10d ago First seen · 57 lines · 81 tokens per session scan A 27ee1c29e183
wiki-lint is a skill published in the GitHub repository shrimbly/project-wiki (5 stars, last pushed 1mo ago), licensed MIT. It adds 81 tokens to every session and 653 once invoked, about $0.0004 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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…