A setup guide for connecting an existing project to an Obsidian-based agent wiki, a shared folder of project knowledge and instructions.

Use it to create or update project instructions, define the wiki scope and issue-tracking conventions, and scaffold a new wiki vault when needed.

It gives agents a consistent place to find project context across sessions instead of relying only on the current conversation.

wiki — Skill by bartolli

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/bartolli/kmd/wiki

Any agent

npx skills add bartolli/kmd --skill wiki

Clone the repo

git clone --depth 1 https://github.com/bartolli/kmd

Made for: Claude Code, Codex.

Or install wiki-sdd, the plugin that ships this one along with the rest of its 9 skills, 5 hooks.

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

When invoked 5,428 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.00259	$0.05428
Opus 5	$0.00130	$0.02714
Sonnet 5	$0.00052	$0.01086
Haiku 4.5	$0.00026	$0.00543

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

Security

Grade B, and why

wiki scanned grade B with 1 finding 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 3d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| MCP registration | `.mcp.json` at the project root, or user-level settings | plugin-bundled, or `[mcp_servers.wiki]` in `~/.codex/config.toml` | `.kiro/settings/mcp.json` (workspace) or `~/.kiro/settings/mcp.json` (use

plugins/claude/wiki-sdd/skills/wiki/SKILL.md · 241 lines

How it starts

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

Wiki — Project Bootstrap

Wire the current project into the ~/llm-wiki agent wiki so wiki-aware skills can find context, scope, and the issue tracker convention. The wiki is the canonical surface for cross-session orientation; this skill is the on-ramp from a consumer project.

This is a prompt-driven bootstrap, not a deterministic script. Explore, present what you found, confirm with the user, then write.

What this skill produces

In the consumer project:

Project instructions (CLAUDE.md, AGENTS.md, or equivalent) populated from templates/project-agents.md.template with three sections: ## First read, ## Wiki integration (carrying WIKI_SCOPE, WIKI_ISSUE_TRACKER, WIKI_TRIAGE_LABELS), and ## Sub-agent spawning.
MCP registration guidance — only when the wiki MCP server is not already available (plugin-bundled or user-registered). Shows the canonical npx @bartolli/kmd mcp --default-root <vault-path> JSON and lets the user place it.

Both are idempotent — if a section/entry already exists, update in place rather than duplicate.

In the vault, only when no vault exists yet (new-vault bootstrap):

Barebone vault structure the MCP server requires — scaffolded by kmd init (starter vault.yaml with empty scopes, the 11 served templates, and the projects/, research/, notes/ domain dirs), the user's first scope then added to vault.yaml per references/vault-yaml.md § Minimal starter. Two forms: kmd init <vault-dir> [--set-default] for a global vault, kmd init --local for a vault the repo carries (§ Local vs global vault).

Mental model

The wiki itself

Three domains (projects/, research/, notes/) under ~/llm-wiki/vault/
A controlled vocabulary of project scopes defined in ~/llm-wiki/vault/vault.yaml under scopes: — adding a new scope requires explicit user approval per the vault blueprint
Two MCP tools: prime(scope, task?) for orientation, search(query, scope?, kind?, limit?) for retrieval
Templates exposed as MCP resources at wiki://template/{domain}/{kind} (11 templates: project-{index, primer, spec, adr, plan, ops, story}, research-{index, article, src}, note) — served from templates/ at the vault root, re-read on every call; a missing file errors at resource-read time

Read the full file on GitHub · 241 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

3d ago First seen · 241 lines · 259 tokens per session scan B ae66d05e23b7

Subscribe to this mod's changes

wiki is a skill published in the GitHub repository bartolli/kmd (7 stars, last pushed 22d ago), licensed MIT. It adds 259 tokens to every session and 5,428 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Memory and context Writing and docs

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

wiki