obsidian-vault-manager

obsidian-vault-manager is a skill for Claude Code from sjungling/sjungling-claude-plugins. It costs 88 tokens per session (1,674 once invoked), scanned A, original, MIT.

A set of instructions for managing an Obsidian vault, which is a folder of linked Markdown notes used by the Obsidian note-taking app. It handles daily notes, templates, tags, searches, and links between notes.

In plain words
What is it for?
Use it to create daily notes, search vault content, organize notes, move notes while preserving links, and write substantial Markdown notes through the Obsidian command-line tool.
Why use it?
It helps change note files and their structure without accidentally breaking Obsidian's internal links. It also accounts for differences between ordinary folders and iCloud-synced vaults.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the technical-writer plugin — 3 skills, 3 commands, 3 agents shipped together

Good fit Use it to create daily notes, search vault content, organize notes, move notes while preserving links, and write substantial Markdown notes through the Obsidian command-line tool.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager
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.

Any agent
npx skills add sjungling/sjungling-claude-plugins --skill obsidian-vault-manager
Clone the repo
git clone --depth 1 https://github.com/sjungling/sjungling-claude-plugins

Made for: Claude Code.

Or install technical-writer, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 3 agents.

Wrote 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.

agentmods badge for obsidian-vault-manager

README.md
[![agentmods](https://agentmods.dev/badge/skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager/github.svg)](https://agentmods.dev/skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager)
Your own site
<a href="https://agentmods.dev/skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager"><img src="https://agentmods.dev/badge/skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager/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.

agentmods 80×15 button for obsidian-vault-manager

Your own site · 80×15
<a href="https://agentmods.dev/skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager"><img src="https://agentmods.dev/badge/skills/sjungling/sjungling-claude-plugins/obsidian-vault-manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,674 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.01674
Opus 5 $0.00044 $0.00837
Sonnet 5 $0.00018 $0.00335
Haiku 4.5 $0.00009 $0.00167

Measured 11d ago against content hash c53033475c2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

obsidian-vault-manager 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 11d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/write-markdown-to-vault.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/technical-writer/skills/obsidian-vault-manager/SKILL.md · 136 lines

How it starts

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

Obsidian Vault Manager

Prerequisites

Before performing vault operations:

  1. Verify obsidian CLI is installed:

    obsidian --version
    

    The CLI is the native obsidian binary that ships with the Obsidian desktop app — not a separate npm package.

  2. List available vaults:

    obsidian vaults
    
  3. Get vault path:

    obsidian vault "<name>" info=path
    

Overview

Use obsidian for vault operations that touch links or structure. For iCloud-synced vaults (path contains Mobile Documents — check with obsidian vault "<name>" info=path), the Write tool is not reliable: iCloud paths are TCC-protected, so direct filesystem writes can be blocked even with the sandbox disabled — only the Obsidian app (via the CLI) is guaranteed to land. For creating a note with substantial content (multi-line, frontmatter, code blocks), use scripts/write-markdown-to-vault.js in this skill — it chunks large payloads under the CLI's ~10KB IPC ceiling, filters banner noise, retries transient errors, and verifies the write by reading the note back. Run it unsandboxed (the CLI hangs under the command sandbox). For vaults on ordinary filesystem paths (not iCloud), the Write tool works directly and is simpler for one-off notes.

Quick Reference

Task Command Notes
List vaults obsidian vaults Always run first
Vault info obsidian vault "<name>" Name, path, file count
Vault path obsidian vault "<name>" info=path Path only, good for scripting
List folders obsidian "vault=<name>" folders Quote vault name if it has spaces
Read note obsidian "vault=<name>" read "<note name>" Reads by name (fuzzy)
Create note (large/iCloud) node scripts/write-markdown-to-vault.js --vault <name> --path <path> --input <file> Chunked, retried, verified — run unsandboxed
Create note (small, non-iCloud) obsidian "vault=<name>" create path="folder/name.md" content="$CONTENT" Use printf to build $CONTENT for multi-line
Overwrite note obsidian "vault=<name>" create path="..." content="$CONTENT" overwrite
Append to note obsidian "vault=<name>" append path="<path>" content="<text>"
Move note obsidian "vault=<name>" move path="old.md" newpath="new.md" Auto-updates all links
Search content obsidian "vault=<name>" search query="<term>" [path=<folder>] [format=json]
Daily note obsidian "vault=<name>" daily Create/open today's note
Active/default vault obsidian vault No name → the vault currently open
Append to daily note obsidian "vault=<name>" daily:append content="<text>" Active vault; needs Daily Notes plugin

Read the full file on GitHub · 136 lines

Files

What ships with it

6 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.

  1. 11d ago First seen · 136 lines · 88 tokens per session scan A c53033475c2d

Subscribe to this mod's changes

obsidian-vault-manager is a skill published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 28d ago), licensed MIT. It adds 88 tokens to every session and 1,674 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens