A refresh tool for a local knowledge base, which stores project information as linked pages. It re-imports pages whose source material has changed and updates their tracking details.

Use it to refresh stale pages, update a changed project entry, or synchronize the knowledge base with its sources.

It keeps project notes aligned with newer source files instead of leaving outdated information in the knowledge base.

kb-sync — Skill by lacolaco

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/lacolaco/claude-plugins/kb-sync

Any agent

npx skills add lacolaco/claude-plugins --skill kb-sync

Clone the repo

git clone --depth 1 https://github.com/lacolaco/claude-plugins

Made for: Claude Code, Codex.

Or install llm-wiki, the plugin that ships this one along with the rest of its 4 skills.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 226 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.

Model	Per session	Once invoked
Fable 5	$0.00054	$0.00226
Opus 5	$0.00027	$0.00113
Sonnet 5	$0.00011	$0.00045
Haiku 4.5	$0.00005	$0.00023

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

Security

Grade A, and why

kb-sync 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.

llm-wiki/skills/kb-sync/SKILL.md · 12 lines

What it actually says

kb-sync (re-ingest stale pages)

Identify target projects from the 陳腐化の疑い section of the kb-lint skill's kb-lint.sh (§3 staleness suspects).
Re-ingest each target with kb-ingest's Ingest procedure, refreshing the page's OKF timestamp field, source_commit, and source_paths (overwriting the existing page). The whole frontmatter must keep satisfying OKF §9.1 (non-empty type).
Update the index if it changed, and append a one-liner sync entry to ~/.knowledge/wiki/log.md under the matching ## YYYY-MM-DD H2 heading (or add a new heading newest-on-top).

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.

3d ago First seen · 12 lines · 54 tokens per session scan A ce35c6a87e24

Subscribe to this mod's changes

kb-sync is a skill published in the GitHub repository lacolaco/claude-plugins (5 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 226 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-31.

Memory and context

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