obsidian-vault

obsidian-vault is a skill for Claude Code from developkiko/DsktpCmndr. It costs 171 tokens per session (2,296 once invoked), scanned A, a copy of obsidian-vault, MIT.

A set of workflows for organizing an Obsidian vault, which is a folder of linked Markdown notes. It covers navigation, note metadata, dashboards, and cleanup.

In plain words
What is it for?
Use it to create Maps of Content and wikilinks, standardize properties, build dashboards, find orphan notes, organize folders, rename or deduplicate notes, and prepare the vault for AI use.
Why use it?
It helps keep a growing collection of notes findable and consistent. It also identifies unlinked notes, duplicates, and disorganized files.

Skill for Claude Code

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

Part of the desktop-commander plugin — 6 skills shipped together

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.

agentmods
npx agentmods add skills/developkiko/dsktpcmndr/obsidian-vault
Any agent
npx skills add developkiko/DsktpCmndr --skill obsidian-vault
Clone the repo
git clone --depth 1 https://github.com/developkiko/DsktpCmndr

Made for: Claude Code.

Or install desktop-commander, the plugin that ships this one along with the rest of its 6 skills.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/developkiko/dsktpcmndr/obsidian-vault.svg)](https://agentmods.dev/skills/developkiko/dsktpcmndr/obsidian-vault)
Your own site
<a href="https://agentmods.dev/skills/developkiko/dsktpcmndr/obsidian-vault"><img src="https://agentmods.dev/badge/skills/developkiko/dsktpcmndr/obsidian-vault.svg" alt="Measured on agentmods" height="20"></a>
Per session 171 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,296 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00171 $0.02296
Opus 5 $0.00086 $0.01148
Sonnet 5 $0.00034 $0.00459
Haiku 4.5 $0.00017 $0.00230

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

Security

Grade A, and why

obsidian-vault 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.

Origin

This is a copy

100% identical to obsidian-vault — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/claude/skills/obsidian-vault/SKILL.md · 209 lines

How it starts

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

Obsidian Vault Assistant

Help the user organize and maintain an Obsidian vault: build navigation with MOCs and wikilinks, normalize metadata, generate dashboards, find and fix orphans, organize folders, deduplicate/rename, and prepare the vault for AI use.

Obsidian-specific facts that shape every rule here:

  • Links are wikilinks resolved by filename, not path: [[Note title]]. Renaming a note auto-updates links inside Obsidian, but moving files outside Obsidian breaks them — always rename via Obsidian when possible.
  • Metadata is Properties (YAML frontmatter) at the top of a note.
  • Dashboards come from Dataview (query language, read-only, flexible) or Bases (native, editable tables, fast on big vaults, properties-only).

Before acting, confirm the vault's root folder and whether the user has the Dataview plugin installed (Bases is built in since Obsidian 1.9). When a request is ambiguous (organize vs. clean up vs. dashboard), ask which task.

  • Basic: [[Three laws of motion]] — resolves by filename, no extension/path.
  • Display text (pipe): [[atomic-habits|James Clear — Atomic Habits]].
  • Heading link: [[Note#Section]]. Block link: [[Note#^block-id]].
  • Embed/transclude: ![[Note]], ![[Note#Section]], ![[image.png]].
  • Aliases: add an aliases property so the note resolves under other names.
  • Avoid # | ^ : % and [ ] in filenames — they have special meaning in links.
  • Prefer wikilinks for internal navigation; use standard Markdown links only if the vault is also published to a tool that can't parse wikilinks.

When adding links, also surface unlinked mentions: if a note's title appears as plain text in other notes, convert those to wikilinks.

Maps of Content (MOCs)

A MOC is a note that links the related notes on a topic — the vault's navigation layer (more flexible than folders or tags, and needs no institutional knowledge).

Conventions:

  • Name MOCs clearly and tag them: tags: [moc] (or a type: moc property) so every MOC is itself discoverable.
  • Keep a top-level Home / Index MOC that links to all topic MOCs.
  • A MOC holds a short intro plus grouped wikilinks; it can be hand-curated or auto-generated with a Dataview/Bases query (see Dashboards).

Read the full file on GitHub · 209 lines

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. 5d ago First seen · 209 lines · 171 tokens per session scan A e0042d5b5439

Subscribe to this mod's changes

obsidian-vault is a skill published in the GitHub repository developkiko/DsktpCmndr (0 stars, last pushed 2mo ago), licensed MIT. It adds 171 tokens to every session and 2,296 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to obsidian-vault, differing in 0 lines, and is treated as a copy.