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-conceptnpx skills add CatChen/knowledge-wiki-template --skill knowledge-wiki-conceptgit clone --depth 1 https://github.com/CatChen/knowledge-wiki-templateWhat 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.00048 | $0.01263 |
| Opus 5 | $0.00024 | $0.00632 |
| Sonnet 5 | $0.00010 | $0.00253 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
knowledge-wiki-concept 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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Wiki Concept
Create or update concept articles in Wiki/Concepts/ by extracting concepts from summary files that have been updated since the last run.
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 summary files to process
Run:
node {KNOWLEDGE_PATH}/scripts/wiki/wiki-state.mjs find-unprocessed-summaries knowledge-wiki-concept
This outputs a JSON array of summary file paths (relative to KNOWLEDGE_PATH) that are new or updated since the last run. Example:
[
"Wiki/Summaries/Posts/Alexa, tell me a joke..summary.md",
"Wiki/Summaries/Posts/Vision Pro 使用体验(Part 1).summary.md"
]
If the array is empty, print Nothing to process. and stop.
3. Process each summary file
For each path in the array from step 2, run the following sub-steps.
3a. Read the summary file
Read the summary file using the Read tool.
Parse the ## Key Concepts section. Each line has the form:
- [[Wiki/Concepts/{concept-slug}|{Display Name}]] — {description}
Extract the slug, display name, and description for each concept.
Also note the summary file's tags frontmatter field — you may draw on these when choosing concept tags, but only include tags that are genuinely relevant to the concept itself.
Derive the summary's link-path by stripping the .md extension from the summary file path, and store it as {summary-link-path}. Example: Wiki/Summaries/Posts/foo.summary.md → Wiki/Summaries/Posts/foo.summary
3b. For each concept, create or update its file
If the concept file does NOT exist, create it:
- Run:
This createsnode {KNOWLEDGE_PATH}/scripts/wiki/wiki-concept.mjs create "{concept-slug}" "{Display Name}"Wiki/Concepts/{concept-slug}.mdwith frontmatter and an empty## Sourcessection. The command prints the file path.
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.
- 3d ago First seen · 126 lines · 48 tokens per session scan A 572eaa600c4e
knowledge-wiki-concept is a skill published in the GitHub repository CatChen/knowledge-wiki-template (105 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 1,263 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…