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.
npx skills add bezata/kObsidian --skill wiki-bootstrapgit clone --depth 1 https://github.com/bezata/kObsidianWrote 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.
[](https://agentmods.dev/skills/bezata/kobsidian/wiki-bootstrap)<a href="https://agentmods.dev/skills/bezata/kobsidian/wiki-bootstrap"><img src="https://agentmods.dev/badge/skills/bezata/kobsidian/wiki-bootstrap/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.
<a href="https://agentmods.dev/skills/bezata/kobsidian/wiki-bootstrap"><img src="https://agentmods.dev/badge/skills/bezata/kobsidian/wiki-bootstrap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00073 | $0.00543 |
| Opus 5.5 | $0.00029 | $0.00217 |
| Sonnet 5.5 | $0.00015 | $0.00109 |
| Haiku 4.5 | $0.00007 | $0.00054 |
Grade A, and why
wiki-bootstrap 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.
What it actually says
Wiki Bootstrap
You are scaffolding an LLM Wiki on top of an Obsidian vault using the
kobsidian MCP server. The vault becomes a compounding knowledge base:
sources flow in, the wiki holds summaries, cross-references, and an index,
and the LLM does the bookkeeping.
When to use
- The user asks to "set up a wiki", "initialize the knowledge base", "start tracking X in a wiki", or "bootstrap this vault".
- The user is new to kObsidian and wants the recommended layout.
wiki.lintreports the wiki is missing, orwiki.queryreturns nothing because the wiki doesn't exist yet.
Steps
-
Confirm vault context. Call
notes.list(orstats.vaultif available) with no directory to verify we're operating on the right vault and to get a sense of existing content. -
Run
wiki.init. With no arguments for defaults (wiki/root, standard folder / file names). If the user specified a custom root, passwikiRoot: "<their-name>". The tool is idempotent — rerunning is safe. -
Show the layout. Read
wiki/wiki-schema.mdback and summarize the conventions to the user in 3-5 lines: the three page types, the log format, and that the wiki is owned by the LLM (they curate sources, you do the bookkeeping). -
Offer the next step. Prompt the user to drop their first source (clipped article, pasted notes, a URL they want to summarize) so you can ingest it with the
wiki-ingestskill.
What not to do
- Do NOT overwrite existing
index.md/log.md/wiki-schema.mdcontent withoutforce: true+ explicit user permission. - Do NOT create scaffolding outside the wiki root; everything lives under
wiki/. - Do NOT invent alternate layouts (flat folders, category prefixes, etc.).
If the user wants a different shape, use env vars or
wikiRootoverride.
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 · 49 lines · 73 tokens per session scan A 52928d4763e0
wiki-bootstrap is a skill published in the GitHub repository bezata/kObsidian (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 543 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
llm-wiki
Build and maintain a persistent, interlinked Obsidian-compatible markdown wiki using Karpathy's LLM Wiki pattern. Extension-backed with auto-generated metadata, guardrails, and 14 custom tools (+3 opt-in agent-trajectory tools).
llm-wiki
Explain and apply the foundational LLM Wiki architecture and knowledge-management strategy. Use for setup, architecture, schema, or organization decisions; operational ingest/query/lint work uses dedicated skills.
wiki-export
Export the Obsidian wiki graph to JSON, GraphML, Neo4j Cypher, Postgres/SQL, HTML, or OKF bundles. Use when transferring or visualizing wiki data in external tools; wiki-import handles the reverse direction.
ObsidianDataWeave: NotebookLM, Atomization, and LLM Wiki
Use when the user wants to control NotebookLM programmatically, import .docx into an Obsidian vault as atomic Zettelkasten notes, build a compiled LLM Wiki layer, or full-text-search the whole vault. Claude Code and Codex both supported.
llm-wiki-orient
Explain the LLM-Wiki pattern, its raw/wiki/schema architecture, how it differs from RAG, GraphRAG and agent memory, and what ready-made solution families exist. Use when the user asks what LLM-Wiki is, whether it is worth adopting, what OpenWiki/wiki memory means, or how the ecosystem fits together.
llm-wiki-local-first-stack
Design a local-first LLM-Wiki stack. Use when the user wants Markdown, git, Obsidian, ripgrep, local embeddings, qmd-style retrieval, SQLite/FTS/vector indexes, local LLMs, offline operation, or safe sync without cloud lock-in; route retrieval/index layer design to llm-wiki-retrieval-architect.