kb-update

kb-update is a skill for Claude Code from waelmas/codeplow. It costs 139 tokens per session (2,324 once invoked), scanned A, original, MIT.

A tool for refreshing an Obsidian project knowledge base after code changes. It reviews recent Git activity and session context, then updates stale notes using evidence from the code.

In plain words
What is it for?
Use it to update existing architecture and research notes, and to flag new concepts for notes that you approve.
Why use it?
It keeps the agent's stored project memory aligned with the current implementation after refactors or other significant changes.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the obsidian-kb plugin — 8 skills, 8 commands shipped together

Good fit Use it to update existing architecture and research notes, and to flag new concepts for notes that you approve.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add waelmas/codeplow
Claude Code
/plugin install obsidian-kb

Made for: Claude Code.

Or install obsidian-kb, the plugin that ships this one along with the rest of its 8 skills, 8 commands.

Wrote 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.

agentmods badge for kb-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/waelmas/codeplow/kb-update/github.svg)](https://agentmods.dev/skills/waelmas/codeplow/kb-update)
Your own site
<a href="https://agentmods.dev/skills/waelmas/codeplow/kb-update"><img src="https://agentmods.dev/badge/skills/waelmas/codeplow/kb-update/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.

agentmods 80×15 button for kb-update

Your own site · 80×15
<a href="https://agentmods.dev/skills/waelmas/codeplow/kb-update"><img src="https://agentmods.dev/badge/skills/waelmas/codeplow/kb-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,324 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00139 $0.02324
Opus 5.5 $0.00056 $0.00930
Sonnet 5.5 $0.00028 $0.00465
Haiku 4.5 $0.00014 $0.00232

Measured 2mo ago against content hash c714180c85bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

kb-update 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 2mo 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.

obsidian-kb/skills/kb-update/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

kb-update - Refresh the KB after code changes

Keep the project KB aligned with reality as the code evolves. Review recent git activity and session context, surgically update stale KB notes, flag new concepts for documentation.

Scope distinction:

  • kb-update (this skill) — edits notes inside the vault (under Architecture/ and Research/, excluding Sessions/ handoffs and Research/Documentation Audit.md) so the agent's memory matches the current code.
  • kb-audit — checks the project's user-owned markdown (README.md, ARCHITECTURE.md, etc.) and produces a stand-alone audit report.

Both enforce the same hard rule: no edit or flag without file:line evidence.

Step 0: Preflight

Follow the Preflight Check in the obsidian-kb awareness skill (${CLAUDE_PLUGIN_ROOT}/skills/obsidian-kb/SKILL.md). In short: verify command -v obsidian, verify timeout 3 obsidian vaults works, launch Obsidian if needed.

Step 1: Resolve the Project Vault

Follow the Vault Resolution Algorithm in ${CLAUDE_PLUGIN_ROOT}/skills/obsidian-kb/SKILL.md. Strict priority: user argument → path overlap → frontmatter project_path → strong name match → STOP and ask.

Capture both $VAULT_NAME and $VAULT_PATH.

Print the confirmation line on your first reply:

"Using vault <Vault Name> at <path> (matched via <tier>). Reviewing KB notes against recent code changes."

If the user passed a focus area in $ARGUMENTS (e.g., "focus on the auth refactor"), capture it as $FOCUS — it will narrow Step 4's inventory.

If no vault exists at all

Tell the user:

"No knowledge base vault found for this project. Run /kb-init to create one first, then return here to refresh it."

Stop.

Step 1b: Vault Access Sequence

Switch Obsidian's active vault to the resolved one so CLI operations work:

CURRENT=$(timeout 3 obsidian vault info=name 2>/dev/null)
if [[ "$CURRENT" != "$VAULT_NAME" ]]; then
  ENCODED=$(printf '%s' "$VAULT_NAME" | sed 's/ /%20/g')
  open "obsidian://open?vault=${ENCODED}"   # macOS; xdg-open on Linux; start on Windows
  sleep 3
  CURRENT=$(timeout 3 obsidian vault info=name 2>/dev/null)
fi
if [[ "$CURRENT" == "$VAULT_NAME" ]]; then CLI_MODE=1; else CLI_MODE=0; fi

Read the full file on GitHub · 215 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. 2mo ago First seen · 215 lines · 139 tokens per session scan A c714180c85bc

Subscribe to this mod's changes

kb-update is a skill published in the GitHub repository waelmas/codeplow (8 stars, last pushed 6mo ago), licensed MIT. It adds 139 tokens to every session and 2,324 once invoked, about $0.0006 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-31.

Related

kb-update compared with skills from other repositories

kb-update next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
kb-updatewaelmas/codeplowSkill86mo agoMITA139Claude Code
knowledge-ingestopenclaw/openclawSkill394kyesterdayMITA80Claude Code, Codex
mem0-oss-to-platformmem0ai/mem0Skill68k2d agoApache-2.0A217Claude Code, Codex
forgetasgeirtj/system_prompts_leaksSkill71k2d agoCC0-1.0A74Claude Code, Codex
Cortexdanielmiessler/LifeOSSkill20kyesterdayMITA184Claude Code
memoryopensquilla/opensquillaSkill7.1k6d agoApache-2.0A44Claude Code, Codex
ha-data-storesshiwenwen/hope-agentSkill1.9kyesterdayMITA115Claude Code, Codex