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-synthesisnpx skills add CatChen/knowledge-wiki-template --skill knowledge-wiki-synthesisgit 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-synthesis)<a href="https://agentmods.dev/skills/catchen/knowledge-wiki-template/knowledge-wiki-synthesis"><img src="https://agentmods.dev/badge/skills/catchen/knowledge-wiki-template/knowledge-wiki-synthesis.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.00061 | $0.01747 |
| Opus 5 | $0.00030 | $0.00873 |
| Sonnet 5 | $0.00012 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00175 |
Grade A, and why
knowledge-wiki-synthesis 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Wiki Synthesis
Discover non-obvious connections across the wiki and write synthesis concept files. Uses a two-phase process: a cheap index-scan to find candidates, then a targeted deep-read to synthesize each one.
Steps
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.
2. Find recently updated summaries
Run:
node {KNOWLEDGE_PATH}/scripts/wiki/wiki-state.mjs find-unprocessed-summaries knowledge-wiki-synthesis
This outputs a JSON array of summary file paths (relative to KNOWLEDGE_PATH) whose summarized_at is newer than the last time this skill ran. On the first run (no prior state), it returns all summary files.
Store this list as RECENT_SUMMARIES. These paths are used as a priority signal in step 4 — candidates that involve at least one recent summary are ranked higher. They are not an exclusive filter; older summaries and concepts are still considered.
3. Load the concept list
Run:
node {KNOWLEDGE_PATH}/scripts/wiki/wiki-index.mjs read-concepts > /tmp/wiki-concepts.md
Then read /tmp/wiki-concepts.md in full using the Read tool, using offset and limit to page through it if the file exceeds the Read tool's line limit. Do not pipe through head or any other truncating command — the concept list may be thousands of lines, and truncating it means missing potential synthesis candidates.
Each line is one concept entry in the form:
- [[Wiki/Concepts/{slug}|{Display Name}]] — {one-line description}
4. Discover connection candidates
Using only the one-line descriptions from step 3, identify 3–5 strong connection candidates. Look for:
| Type | What to look for |
|---|---|
cross-cutting |
A theme that appears across multiple unrelated summaries or concepts |
relationship |
Two or more concepts that seem deeply related but are not explicitly linked |
contradiction |
Two summaries or concepts that appear to take opposing positions on the same topic |
gap |
A theme strongly implied by multiple entries but with no dedicated concept article |
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 · 178 lines · 61 tokens per session scan A 8f8f3459ae3a
knowledge-wiki-synthesis is a skill published in the GitHub repository CatChen/knowledge-wiki-template (105 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 1,747 once invoked, about $0.0003 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…