kb-audit

A command that checks Markdown documentation against the project's actual code. It looks through files such as the README, architecture notes, contribution guide, and documentation folder.

In plain words
What is it for?
Use it during documentation refreshes or before a major rewrite to list stale statements in an Obsidian project vault.
Why use it?
It helps find documentation claims that have become outdated and backs each finding with the relevant file and line.

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-audit
Clone the repo
git clone --depth 1 https://github.com/waelmas/codeplow
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 190 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.00022 $0.00190
Opus 5 $0.00011 $0.00095
Sonnet 5 $0.00004 $0.00038
Haiku 4.5 $0.00002 $0.00019

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

Security

Grade A, and why

kb-audit 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-audit.md · 16 lines

What it actually says

/kb-audit

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

Audits the existing markdown docs in the current project (README, ARCHITECTURE, CONTRIBUTING, docs/*, etc.) against the actual code. Produces a "Documentation Audit" note in the project's Obsidian vault listing every stale claim with file:line evidence.

Re-runnable any time. Use for quarterly doc refreshes or before a major rewrite.

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 · 16 lines · 22 tokens per session scan A d7e053377016

Subscribe to this mod's changes

kb-audit is a command published in the GitHub repository waelmas/codeplow (8 stars, last pushed 4mo ago), licensed MIT. It adds 22 tokens to every session and 190 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.