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 agentmods add skills/ar9av/obsidian-wiki/memory-bridgenpx skills add Ar9av/obsidian-wiki --skill memory-bridgegit 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/memory-bridge)<a href="https://agentmods.dev/skills/ar9av/obsidian-wiki/memory-bridge"><img src="https://agentmods.dev/badge/skills/ar9av/obsidian-wiki/memory-bridge.svg" alt="Measured on agentmods" 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 | $0.00134 | $0.01655 |
| Opus 5 | $0.00067 | $0.00827 |
| Sonnet 5 | $0.00027 | $0.00331 |
| Haiku 4.5 | $0.00013 | $0.00166 |
Grade A, and why
memory-bridge 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 5d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Bridge — Cross-Tool Knowledge Browser
You are helping the user browse and compare their Obsidian wiki knowledge filtered by which AI tool originally produced it. The wiki tracks source provenance in .manifest.json and page sources: frontmatter — this skill surfaces that metadata as a navigable view.
Before You Start
- Resolve config — follow the Config Resolution Protocol in
llm-wiki/SKILL.md(inline@nameoverride → walk up CWD for.env→ global config → prompt setup). This givesOBSIDIAN_VAULT_PATH. - Read
$OBSIDIAN_VAULT_PATH/.manifest.json— this is the source-of-truth for what tool produced what. - Read
$OBSIDIAN_VAULT_PATH/index.mdfor page titles and one-line descriptions.
Commands
Parse the user's invocation to determine mode:
| Invocation | Mode |
|---|---|
/memory-bridge <tool> |
Browse — list all wiki pages sourced from <tool> |
/memory-bridge <tool> "<topic>" |
Search — pages from <tool> that mention <topic> |
/memory-bridge diff |
Diff — pages unique to each tool; overlap; blind spots |
/memory-bridge diff <tool-a> <tool-b> |
Diff — compare two specific tools |
/memory-bridge map |
Map — full origin matrix: every page × every tool that touched it |
Recognized tool names: claude, codex, hermes, openclaw, copilot, pi, manual (hand-written), ingest (wiki-ingest documents).
Step 1: Build the Source Map
Read .manifest.json. For each source entry, extract:
source_type— maps to tool name:claude_conversation,claude_memory,claude_audit_log,claude_desktop_session→claudecodex_rollout,codex_index,codex_history→codexhermes_memory,hermes_session→hermesopenclaw_memory,openclaw_daily_note,openclaw_session,openclaw_dreams→openclawcopilot_session,copilot_checkpoint,copilot_transcript,copilot_memory_artifact→copilotpi_session→pidocument→ingest- anything else →
manual
pages_createdandpages_updated— the wiki pages that came out of this source
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.
- 5d ago First seen · 164 lines · 134 tokens per session scan A 29b175437680
memory-bridge is a skill published in the GitHub repository Ar9av/obsidian-wiki (3,348 stars, last pushed 2d ago), licensed MIT. It adds 134 tokens to every session and 1,655 once invoked, about $0.0007 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
Obsidian 知识库全生命周期管理：三层架构、素材入库(ABC分级)、健康检查、GBrain/GraphRAG/LLM Wiki 三件套集成、目录整理.
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.