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
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 Ar9av/obsidian-wiki --skill wiki-context-packgit clone --depth 1 https://github.com/Ar9av/obsidian-wikiWrote 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/wiki-context-pack)<a href="https://agentmods.dev/skills/ar9av/obsidian-wiki/wiki-context-pack"><img src="https://agentmods.dev/badge/skills/ar9av/obsidian-wiki/wiki-context-pack.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00063 | $0.00807 |
| Opus 5 | $0.00032 | $0.00404 |
| Sonnet 5 | $0.00013 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
wiki-context-pack 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wiki Context Pack
This is a read-only skill. It must not modify the vault, including log.md,
index.md, hot.md, or .manifest.json.
Before You Start
-
Resolve config using the Config Resolution Protocol in
llm-wiki/SKILL.md: inline@name, then walk up from CWD for.env, then the global config. -
If
$OBSIDIAN_VAULT_PATH/AGENTS.mdexists, read it as trusted owner conventions. Do not include that file as a knowledge excerpt. -
Canonicalize the configured vault to a physical absolute path before invocation:
OBSIDIAN_VAULT_PATH="$(cd "$OBSIDIAN_VAULT_PATH" && pwd -P)"If this fails, report that the configured vault path is invalid.
-
Parse:
- topic, required unless
--recent; --budget N, default8000;--recent;--public-only;--metadata-only;--json.
- topic, required unless
Execute
Build the requested arguments, then prefer the installed executable:
obsidian-wiki context-pack --vault "$OBSIDIAN_VAULT_PATH" "<topic>" --budget 8000
For recent activity:
obsidian-wiki context-pack --vault "$OBSIDIAN_VAULT_PATH" --recent --budget 8000
Append the requested flags exactly. If obsidian-wiki is unavailable but
$OBSIDIAN_WIKI_REPO/obsidian_wiki/cli.py exists, run the same arguments from
that configured clone:
python3 -m obsidian_wiki.cli context-pack --vault "$OBSIDIAN_VAULT_PATH" "<topic>" --budget 8000
Use the executable-or-clone fallback explicitly:
if command -v obsidian-wiki >/dev/null 2>&1; then
obsidian-wiki context-pack --vault "$OBSIDIAN_VAULT_PATH" "<topic>" --budget 8000
elif [ -n "${OBSIDIAN_WIKI_REPO:-}" ] && [ -f "$OBSIDIAN_WIKI_REPO/obsidian_wiki/cli.py" ]; then
(
cd "$OBSIDIAN_WIKI_REPO"
python3 -m obsidian_wiki.cli context-pack --vault "$OBSIDIAN_VAULT_PATH" "<topic>" --budget 8000
)
else
# Tell the user to run: pip install obsidian-wiki
# or rerun setup from a valid clone.
fi
For --recent, substitute --recent for "<topic>" and keep the default
--budget 8000. If neither invocation route exists, give the user the
actionable guidance pip install obsidian-wiki or rerun setup from a valid clone; do not silently fall back to manually loading the whole vault.
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.
- 8d ago First seen · 90 lines · 63 tokens per session scan A 23c7c372f2f3
wiki-context-pack is a skill published in the GitHub repository Ar9av/obsidian-wiki (3,371 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 807 once invoked, about $0.0003 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.
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).
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.
link-retrieve
Use before answering work that may depend on user memory, project history, source-backed notes, or prior decisions; retrieve compact Link context through the CLI without loading the whole wiki or requiring MCP.
link-ingest
Use when raw files are present, source pages look stale, or a user asks to ingest notes into Link; refresh source-backed wiki pages, propose memories, and validate updates through the CLI without MCP.