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/cogni-work/insight-wave/knowledge-lintnpx skills add cogni-work/insight-wave --skill knowledge-lintgit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/cogni-work/insight-wave/knowledge-lint)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/knowledge-lint"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-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.00118 | $0.02511 |
| Opus 5 | $0.00059 | $0.01256 |
| Sonnet 5 | $0.00024 | $0.00502 |
| Haiku 4.5 | $0.00012 | $0.00251 |
Grade A, and why
knowledge-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 yesterday.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Lint
Run the semantic lint pass on a cogni-knowledge base — surface stale pages, stale drafts, claim drift, missing reverse links, entries-count drift, and formatting findings, and optionally repair the mechanical classes with --fix. This is the standalone analog of cogni-wiki:wiki-lint, computed natively on the vendored lint_wiki.py engine (resolved vendored-first via resolve_wiki_scripts()), so a Karpathy base is lintable with no cogni-wiki plugin installed.
Lint is read-only by default (a pure audit). It writes to the wiki only when the user passes --fix — and even then only the mechanical, deterministic repair classes the engine owns. This is the tokenful semantic counterpart to knowledge-health's cheap structural gate: run health first, reach for lint when you want to inspect or repair drift.
Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once at the start of a session so you remember the wiki-engine boundary — cogni-knowledge runs the lint pass on the vendored wiki-lint engine, it does not dispatch cogni-wiki:wiki-lint.
When to run
- User asks to lint, audit hygiene, or find/fix stale content in a knowledge base
- After noticing entries-count or claim drift in
knowledge-healthand wanting to reconcile it - Periodically as a maintenance pass on a compounding base
- Before a
knowledge-finalizerun, to clean reverse links and drift the synthesis would otherwise inherit
Never run when
- The target directory has no
.cogni-knowledge/binding.json— offerknowledge-setupinstead.
How it relates to neighbours
knowledge-healthis the cheap structural integrity gate (vendoredhealth.py);knowledge-lintis the semantic hygiene pass (vendoredlint_wiki.py). They share the bound base but answer different questions — run health for "is it broken?", lint for "is it stale / can it be tidied?".knowledge-finalizealready runslint --fix=allas its deposit-time conformance gate. This skill exposes the full lint CLI for deliberate, operator-driven runs (audit,--suggest, selective--fix=<class>).
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.
- yesterday Changed · -13 lines f8b62f79b584
- 5d ago First seen · 150 lines · 118 tokens per session scan A 78badcfb837b
knowledge-lint is a skill published in the GitHub repository cogni-work/insight-wave (12 stars, last pushed today), licensed Apache-2.0. It adds 118 tokens to every session and 2,511 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-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…