kb-update

A command that refreshes an existing project's Obsidian knowledge-base notes after code changes. You can optionally tell it which part of the project deserves attention.

In plain words
What is it for?
Use it after refactoring or other code changes to update project notes, with an optional focus such as an authentication change.
Why use it?
Documentation can become inaccurate as code evolves. This command helps bring the notes back in line with the current implementation.

Command

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 commands/waelmas/codeplow/kb-update
Clone the repo
git clone --depth 1 https://github.com/waelmas/codeplow
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 127 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.00017 $0.00127
Opus 5 $0.00009 $0.00063
Sonnet 5 $0.00003 $0.00025
Haiku 4.5 $0.00002 $0.00013

Measured 2d ago against content hash 6f60f917385f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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/commands/kb-update.md · 14 lines

What it actually says

/kb-update

Trigger the kb-update skill. Read the instructions from ${CLAUDE_PLUGIN_ROOT}/skills/kb-update/SKILL.md in this plugin and follow them exactly.

The user's arguments (if any) can include a vault name hint and/or a focus area to prioritize (e.g. "focus on the auth refactor").

User arguments: $ARGUMENTS

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. 2d ago First seen · 14 lines · 17 tokens per session scan A 6f60f917385f

Subscribe to this mod's changes

kb-update is a command published in the GitHub repository waelmas/codeplow (8 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 127 once invoked, about $0.0001 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.