A synchronisation routine that compares recent code changes with a project's knowledge base and updates documentation when appropriate. It treats source specifications and claim records as authoritative rather than generated notes.

It is for reviewing recent Git changes, finding affected documentation, reconciling code with project claims, and keeping the knowledge base current.

It reduces the risk that project documentation describes old APIs, types, or rules. It also flags contradictions instead of silently rewriting the knowledge base.

kb-update — Command for Claude Code by mathiasbourgoin/roster

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.

Clone the repo

git clone --depth 1 https://github.com/mathiasbourgoin/roster

Made for: Claude Code.

Or install roster, the plugin that ships this one along with the rest of its 40 commands, 8 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mathiasbourgoin/roster/kb-update/github.svg)](https://agentmods.dev/commands/mathiasbourgoin/roster/kb-update)

Your own site

<a href="https://agentmods.dev/commands/mathiasbourgoin/roster/kb-update"><img src="https://agentmods.dev/badge/commands/mathiasbourgoin/roster/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mathiasbourgoin/roster/kb-update"><img src="https://agentmods.dev/badge/commands/mathiasbourgoin/roster/kb-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Model	Per session	Once invoked
Fable 5.1	$0.00021	$0.00949
Opus 5.5	$0.00008	$0.00380
Sonnet 5.5	$0.00004	$0.00190
Haiku 4.5	$0.00002	$0.00095

Measured 1mo ago against content hash d6bbae5a4bc5, 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 1mo 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/commands/kb-update.md · 82 lines

How it starts

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

KB Update

Synchronize the project knowledge base with recent changes. This is the standalone invocable version of the KB agent's update mode.

Steps

1. Read KB Structure

Run the claims reconciler's audit --root . subcommand when either scripts/claims-reconcile.js or .harness/bin/claims-reconcile.js is available. Treat specs/*.md, specs/claims-authority.json, and specs/claims.lock as authoritative inputs; generated KB files are views, never evidence for their own source claims.
Read kb/index.md to understand the KB layout and file purposes.
Identify all KB files: spec.md, properties.md, glossary.md, architecture.md, and any domain-specific files listed in the index.

2. Identify Recent Changes

Run git diff HEAD~5..HEAD --name-only to find recently changed source files (adjust range if user specifies).
Run git diff HEAD~5..HEAD for the actual diffs.
Identify which KB-relevant concepts were touched (new types, changed APIs, modified invariants, renamed terms).

3. Compare Code Against KB

For each changed concept, classify the delta:

Delta Type	Action
Code contradicts KB spec	FLAG AS ERROR. Do NOT update KB. Report: "Code at `<file>:<line>` violates spec: `<quote>`. Fix the code or open a spec amendment discussion."
Code extends KB (new feature, new term)	Add entries to relevant KB files. Update `kb/index.md` if new files created.
Code refines existing concept	Update the KB entry with more precise language. Preserve or strengthen existing properties.
KB entry has no corresponding code	Flag as potentially stale. Do not remove — ask the user.

4. Apply Updates

When the claims reconciler is installed, do not hand-edit generated normative sections in kb/spec.md, kb/properties.md, or kb/index.md. Amend the authoritative spec or metadata, validate it, then run the reconciler's project --root . subcommand.
Preserve the optional code-intel block in kb/properties.md; the projector owns the rest of that generated file.
For each KB file modified, update the frontmatter last-updated field to today's date.
Add cross-references between related entries.
Ensure new terms are added to kb/glossary.md with definitions.

Read the full file on GitHub · 82 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.

1mo ago First seen · 82 lines · 21 tokens per session scan A d6bbae5a4bc5

Subscribe to this mod's changes

kb-update is a command published in the GitHub repository mathiasbourgoin/roster (2 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 949 once invoked, about $0.0001 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-09-07.

Memory and context Writing and docs

kb-update

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

KB Update

Steps

1. Read KB Structure

2. Identify Recent Changes

3. Compare Code Against KB

4. Apply Updates

What this file has done since we first saw it

Other commands, from other repositories

minutes-ideas

learn

memory-store

analyze-context

cc-memory

lians-recall