knowledge-wiki-concept

A tool that creates or updates concept articles in a knowledge wiki from summary files. It processes summaries that are new or changed since its previous run.

In plain words
What is it for?
Use it to populate or refresh the Wiki/Concepts folder after summaries are created or updated. It extracts the listed key concepts from each summary.
Why use it?
It turns collected summaries into organized concept notes, so the wiki can be refreshed as source material changes. It avoids reprocessing summaries that have not changed.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/catchen/knowledge-wiki-template/knowledge-wiki-concept
Any agent
npx skills add CatChen/knowledge-wiki-template --skill knowledge-wiki-concept
Clone the repo
git clone --depth 1 https://github.com/CatChen/knowledge-wiki-template

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 572eaa600c4e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/skills/knowledge-wiki-concept/SKILL.md · 126 lines

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.mdWiki/Summaries/Posts/foo.summary


3b. For each concept, create or update its file

If the concept file does NOT exist, create it:

  1. Run:
    node {KNOWLEDGE_PATH}/scripts/wiki/wiki-concept.mjs create "{concept-slug}" "{Display Name}"
    
    This creates Wiki/Concepts/{concept-slug}.md with frontmatter and an empty ## Sources section. The command prints the file path.

Read the full file on GitHub · 126 lines

Changes

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.

  1. 3d ago First seen · 126 lines · 48 tokens per session scan A 572eaa600c4e

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens