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/catchen/knowledge-wiki-template/knowledge-wiki-lintnpx skills add CatChen/knowledge-wiki-template --skill knowledge-wiki-lintgit clone --depth 1 https://github.com/CatChen/knowledge-wiki-templateWrote 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/catchen/knowledge-wiki-template/knowledge-wiki-lint)<a href="https://agentmods.dev/skills/catchen/knowledge-wiki-template/knowledge-wiki-lint"><img src="https://agentmods.dev/badge/skills/catchen/knowledge-wiki-template/knowledge-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 | $0.00043 | $0.03546 |
| Opus 5 | $0.00022 | $0.01773 |
| Sonnet 5 | $0.00009 | $0.00709 |
| Haiku 4.5 | $0.00004 | $0.00355 |
Grade A, and why
knowledge-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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Wiki Lint
Health-check and repair the wiki. Runs twelve checks in sequence — each builds on a clean state left by the previous one. JavaScript handles all file-system detection; the LLM handles any repair that requires judgment.
Setup
1. Establish the working directory
The knowledge base root is the Git repository root. Run git rev-parse --show-toplevel and store the result as KNOWLEDGE_PATH.
Use KNOWLEDGE_PATH for all subsequent steps.
Check 1 — Orphan Summaries
Deletes summary files whose source document has been moved or deleted.
2. Find orphan summaries
Run:
node {KNOWLEDGE_PATH}/scripts/wiki/wiki-lint.mjs find-orphan-summaries
Output is a JSON object keyed by orphan summary file path (relative to KNOWLEDGE_PATH). Each value has a source field with the path the summary expected to find, or null if the frontmatter had no source field.
If the object is empty ({}), skip to Check 2 and print Check 1: no orphan summaries.
3. Delete orphan summary files and remove their index entries
For each key in the output:
- Delete the file at
{KNOWLEDGE_PATH}/{key}. - Derive the summary's rel-path by stripping the
Wiki/Summaries/prefix and the.mdextension from the key. Example:Wiki/Summaries/Posts/Foo.summary.md→Posts/Foo.summary. Then run:node {KNOWLEDGE_PATH}/scripts/wiki/wiki-index.mjs delete-summary "{rel-path}"
After processing all orphans, delete any now-empty directories under Wiki/Summaries/:
find {KNOWLEDGE_PATH}/Wiki/Summaries -type d -empty -delete
Check 2 — Broken Summary → Concept Links
Creates missing concept files referenced by summaries.
4. Find and repair broken summary → concept links
Run:
node {KNOWLEDGE_PATH}/scripts/wiki/wiki-lint.mjs find-broken-summary-links
Output is a JSON object keyed by missing concept file path. Each value has a referencedBy array listing the summary files that link to that missing concept.
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 · 379 lines · 43 tokens per session scan A e65d8190e10c
knowledge-wiki-lint is a skill published in the GitHub repository CatChen/knowledge-wiki-template (105 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 3,546 once invoked, about $0.0002 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.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…