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 agentmods add skills/keysersoose/claude-code-setup/wiki-lintnpx skills add keysersoose/claude-code-setup --skill wiki-lintgit clone --depth 1 https://github.com/keysersoose/claude-code-setupWrote 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/keysersoose/claude-code-setup/wiki-lint)<a href="https://agentmods.dev/skills/keysersoose/claude-code-setup/wiki-lint"><img src="https://agentmods.dev/badge/skills/keysersoose/claude-code-setup/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.00110 | $0.00777 |
| Opus 5 | $0.00055 | $0.00388 |
| Sonnet 5 | $0.00022 | $0.00155 |
| Haiku 4.5 | $0.00011 | $0.00078 |
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 5d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wiki-lint — wiki maintenance pass
The wiki is the codebase; this is its test suite. WIKI = the global knowledge base path defined in your global CLAUDE.md. It is a git repo — every lint run ends with a commit, so damage is always recoverable.
Checks (run all, cheap subagents for the reading)
Delegate bulk reading to a cheap subagent that returns findings as a packet; verify load-bearing claims yourself before editing (leads, not facts).
- Index freshness — does every status line in
index.mdmatch the current reality in its project page AND the actual repo state (git log dates, status files)? The index is the highest-traffic file; it rots first. - Stale claims — frontmatter
updated:older than 30 days on an ACTIVE project's page = suspect. Cross-check the 2-3 most load-bearing claims per stale page against reality (repo, status files). Fix or mark. - Contradictions — same fact stated differently in two places (index vs page, page vs me/, wiki vs project CLAUDE.md). One fact, one place: fix the copies to reference the canonical location.
- Orphans — pages nothing links to (grep for
[[name]]and](pathreferences). Either link them from the right index/_index page or propose deletion. - Broken links —
[[wikilinks]]and relative markdown links pointing at files that don't exist. Fix or remove. - Delete-when-wrong sweep — anything proven false (old model names, dead tools, superseded decisions): DELETE the claim, don't annotate around it. Update an existing page rather than creating a duplicate; delete notes that turn out to be wrong.
- Log hygiene — daily logs are append-only (never rewrite), but check the last week's rich summaries exist; a run of marker-only days means the session-end summaries aren't being written — flag it.
- Size guard —
index.mdshould stay under ~60 lines of content; me/ files under ~30. If growing, tighten: statuses move to pages, index keeps one line each.
Output
- Apply all safe fixes directly (index refresh, link repair, deletions of proven-wrong claims,
updated:bumps). git -C <WIKI> add -A && git commitwith messagelint: <date> — <n> fixes, <n> flags.- Report to the user: fixes applied, contradictions that needed judgment, anything flagged for them (risks noted in pages, decisions only they can make).
- Append a one-line entry to today's log:
## [YYYY-MM-DD] lint | wiki | <n> fixes.
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.
- 5d ago First seen · 40 lines · 110 tokens per session scan A 6aacaa7d24e8
wiki-lint is a skill published in the GitHub repository keysersoose/claude-code-setup (2 stars, last pushed 2mo ago), licensed MIT. It adds 110 tokens to every session and 777 once invoked, about $0.0006 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…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…