Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cogni-work/insight-wave/plugin install cogni-knowledgeWrote 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-refresh)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/knowledge-refresh"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-refresh/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/cogni-work/insight-wave/knowledge-refresh"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/knowledge-refresh.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.00182 | $0.09106 |
| Opus 5.5 | $0.00073 | $0.03642 |
| Sonnet 5.5 | $0.00036 | $0.01821 |
| Haiku 4.5 | $0.00018 | $0.00911 |
Grade A, and why
knowledge-refresh 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 1mo 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Refresh
Close the self-healing loop for a bound cogni-knowledge base. Wiki pages age — the vendored lint_wiki.py flags stale_page (>365d) and stale_draft (>180d) findings, but lint alone doesn't bring fresh evidence. Push-mode lints the wiki, asks the user which stale topics they want fresh evidence on, then runs the inverted pipeline per selected topic: the seven-phase chain knowledge-plan → knowledge-curate → knowledge-fetch → knowledge-ingest → knowledge-distill (optional, fail-soft) → knowledge-compose → knowledge-verify → knowledge-finalize. Each topic ends with a freshly-composed, claim-verified type: synthesis page deposited into the bound wiki, and the distill step enriches the concept/entity web. An orthogonal opt-in --resweep flag re-verifies the bound wiki's cited claims against live source URLs.
This skill is a pure orchestrator — push-mode composes existing cogni-knowledge phase skills via Skill(...), never re-implementing them. Push-mode dispatches zero cogni-research skills — cogni-research is 0% of the runtime path.
Read ${CLAUDE_PLUGIN_ROOT}/references/delegation-contract.md once per session to remember the delegation boundary and the Skill-dispatch convention (§"How Skill(...) blocks are written").
When to run
- User wants to refresh stale pages in a bound knowledge base
- User wants the system to auto-research the stale topics (push-mode)
- User wants to re-verify the bound wiki's cited claims against live source URLs —
--resweep(opt-in)
Never run when
- No
binding.jsonexists at the resolved knowledge root — route to/cogni-knowledge:knowledge-setup - The bound wiki has zero stale pages AND
--mode push— there's nothing to push-refresh --mode push(or the default) was selected but the vendoredwiki-lintscript (lint_wiki.py) is missing from this install — abort with the standard missing-vendored-scripts message (Step 0 pre-flight)--resweepwas passed but the vendored wiki-claims-resweep scripts are missing from this install — abort with the standard missing-vendored-scripts message (Step 0 pre-flight)
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.
- 1mo ago Changed · +3 lines eee809ed0851
- 1mo ago First seen · 297 lines · 182 tokens per session scan A d4dfa1fcbf9a
knowledge-refresh is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 182 tokens to every session and 9,106 once invoked, about $0.0007 per session on Opus 5.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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn). Routes meetings to knowledge-meeting-ingest and short thoughts…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
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…
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…