A tool for creating an empty Obsidian vault, which is a folder of linked Markdown notes, for a project. It creates the folders and placeholder notes without examining the codebase.

Use it to create a bare project vault and its placeholders; use a fuller initialization process when you also need code analysis and documentation auditing.

It sets up a consistent knowledge-base structure when you are not ready to populate it with project analysis.

kb-scaffold — Skill by waelmas

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/waelmas/codeplow/kb-scaffold

Any agent

npx skills add waelmas/codeplow --skill kb-scaffold

Clone the repo

git clone --depth 1 https://github.com/waelmas/codeplow

Made for: Claude Code, Codex.

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

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

When invoked 4,935 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.00102	$0.04935
Opus 5	$0.00051	$0.02468
Sonnet 5	$0.00020	$0.00987
Haiku 4.5	$0.00010	$0.00494

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

Security

Grade A, and why

kb-scaffold 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/skills/kb-scaffold/SKILL.md · 419 lines

How it starts

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

kb-scaffold - Create an Empty Project Knowledge Base

Create a new Obsidian vault with a standardized empty structure. This is the lightweight alternative to kb-init - use when the user wants just the folders and placeholders, without automated codebase analysis.

For the full flow (scaffold + populate + audit), direct the user to kb-init instead.

Step 0: Preflight - Obsidian available and running?

Follow the Preflight Check in the obsidian-kb awareness skill (${CLAUDE_PLUGIN_ROOT}/skills/obsidian-kb/SKILL.md). In short:

command -v obsidian - if missing, check if the app is installed; if neither, show cross-platform install instructions (brew install --cask obsidian / flatpak install flathub md.obsidian.Obsidian / winget install Obsidian.Obsidian, or https://obsidian.md/download) and stop.
timeout 3 obsidian vaults - if it fails, launch Obsidian (open -a Obsidian on macOS, equivalent for Linux/Windows), wait 2-3 seconds, retry.
Only proceed once obsidian vaults succeeds.

Step 1: Check for Existing Vaults (strict priority)

Follow the Vault Resolution Algorithm in ${CLAUDE_PLUGIN_ROOT}/skills/obsidian-kb/SKILL.md. Use strict priority order:

Path overlap - exactly one vault whose path is inside $PWD or vice versa.
Frontmatter project_path - a root note's YAML matches $PWD exactly.
Strong name match - word-boundary substring match, exactly one candidate.

If a match at any tier exists, treat that vault as a potential existing KB for this project and follow the "If a matching or similar vault is found" branch below.

If none of the tiers match, there's no existing vault - proceed to Step 2 to scaffold a new one.

Critical: every subsequent obsidian command in this skill MUST include vault="<name>" with the explicit vault name.

If a matching or similar vault is found

Present the finding to the user and ask them to choose:

"I found an existing vault [vault name] at [path] that appears to be associated with this project. Would you like to:

Use it - adopt this vault as the project KB (I'll update its Index.md with the project path if needed)

Delete and recreate - remove this vault and create a fresh one

Ignore it - create a new vault alongside it with a different name"

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

2d ago First seen · 419 lines · 102 tokens per session scan A b95b04b99251

Subscribe to this mod's changes

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