obsidian-wiki is a framework that helps AI agents build and maintain an interconnected knowledge base from text-based material in an Obsidian vault. It is for people who want their agents to remember discoveries, connect related information, and answer questions with wiki-link citations. Catalogue add-ons provide the agent skills, instructions, agents, and configuration used to create and maintain these wikis.
Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Ar9av/obsidian-wikinpx agentmods add skills/ar9av/obsidian-wiki/vault-skill-factoryWrote 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/ar9av/obsidian-wiki/vault-skill-factory)<a href="https://agentmods.dev/skills/ar9av/obsidian-wiki/vault-skill-factory"><img src="https://agentmods.dev/badge/skills/ar9av/obsidian-wiki/vault-skill-factory/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/ar9av/obsidian-wiki/vault-skill-factory"><img src="https://agentmods.dev/badge/skills/ar9av/obsidian-wiki/vault-skill-factory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 23 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00172 | $0.02035 |
| Opus 5 | $0.00086 | $0.01018 |
| Sonnet 5 | $0.00034 | $0.00407 |
| Haiku 4.5 | $0.00017 | $0.00203 |
Grade A, and why
vault-skill-factory 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- beeweave-vault-skill-factory — 88% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Skill Factory
You turn a cluster of mature, curated wiki pages into a portable Agent Skill: a
SKILL.md plus a references/ folder, written to a review directory for the human to inspect
and (only if they choose) install. This is the inverse of wiki-capture: capture turns a
conversation into a page; the factory turns a body of pages into a reusable skill.
Hard guardrails (read first)
- Never write into
.skills/and never runsetup.shor create symlinks into any global skill directory (~/.claude/skills,~/.codex/skills, …). Generated skills go to the review dir only. Installation is a separate, explicit human decision. - Never auto-install. End by telling the user where the skill is and how to install it project-locally if they want — do not do it for them.
- Source pages are trusted vault content, but do not invent capabilities: the generated skill must reflect what the pages actually say.
Before You Start
- Resolve config (Config Resolution Protocol in
llm-wiki/SKILL.md): getOBSIDIAN_VAULT_PATH,OBSIDIAN_WIKI_REPO,OBSIDIAN_LINK_FORMAT, the QMD vars, and:SKILL_FACTORY_OUTPUT_DIR— where generated skills land. Default:$OBSIDIAN_VAULT_PATH/_generated-skills(a vault-level, underscore-prefixed excluded dir — like_raw/_staging/_sources, NOT theskills/knowledge category). This co-locates generated skills with the vault they were distilled from. Create it if missing. Note:_generated-skills/holds runtime Agent-Skill bundles (name+descriptionfrontmatter), not wiki pages — never write them intoskills/(that category is for knowledge pages and is graph-/lint-/index-tracked).SKILL_FACTORY_MATURITY— comma list oflifecycle:values that count as "mature". Default:reviewed,verified. Pages withtier: corealso qualify.
- Read
index.mdto understand what the vault holds.
Step 1: Choose the cluster
Decide which pages become the skill. The user may name a topic, tag, or project; otherwise propose candidates.
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.
- 12d ago First seen · 144 lines · 172 tokens per session scan A 3acb03105495
vault-skill-factory is a skill published in the GitHub repository Ar9av/obsidian-wiki (3,393 stars, last pushed yesterday), licensed MIT. It adds 172 tokens to every session and 2,035 once invoked, about $0.0009 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-30.
Other skills, from other repositories
knowledge-base-management
A lifecycle system for managing an Obsidian knowledge base, which is a folder of linked notes. It organizes raw material, AI-maintained wiki pages, and generated views into separate layers.
llm-wiki
Maintain a personal team knowledge base using the LLM Wiki pattern — incremental ingest, query, and lint operations on a layered wiki architecture.
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
orchestrations
Pick and run a multi-phase workflow that chains foundational task skills (git-wrapup, release-and-publish, maintenance, field-test, setup, etc.) end-to-end. Routes user intent to a workflow file under workflows/ — greenfield builds, maintenance + release, field-test + fix, or known-work + release. Single source for…