obsidian-vault

obsidian-vault is an agent for Claude Code from takashito/claude-obsidian-chronicle. It costs 266 tokens per session (2,715 once invoked), scanned B, original, MIT.

A helper agent for managing an Obsidian vault, which is Obsidian's folder of notes and related data. It handles vault content according to Obsidian conventions such as links, metadata, daily notes, canvases, and bases.

In plain words
What is it for?
Use it to create, change, append, read, search, organize, analyze, or delete vault data. It can also manage tasks, canvases, bases, and session records.
Why use it?
It prevents vault operations from being treated as ordinary text-file edits that could lose Obsidian-specific meaning. It also resolves which vault to use for each project.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT variable. Also seen: model in frontmatter; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the obsidian-chronicle plugin — 2 commands, 1 agent shipped together

Good fit Use it to create, change, append, read, search, organize, analyze, or delete vault data. It can also manage tasks, canvases, bases, and session records.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add takashito/claude-obsidian-chronicle
Claude Code
/plugin install obsidian-chronicle

Made for: Claude Code.

Or install obsidian-chronicle, the plugin that ships this one along with the rest of its 2 commands, 1 agent.

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/agents/takashito/claude-obsidian-chronicle/obsidian-vault/github.svg)](https://agentmods.dev/agents/takashito/claude-obsidian-chronicle/obsidian-vault)
Your own site
<a href="https://agentmods.dev/agents/takashito/claude-obsidian-chronicle/obsidian-vault"><img src="https://agentmods.dev/badge/agents/takashito/claude-obsidian-chronicle/obsidian-vault/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

Your own site · 80×15
<a href="https://agentmods.dev/agents/takashito/claude-obsidian-chronicle/obsidian-vault"><img src="https://agentmods.dev/badge/agents/takashito/claude-obsidian-chronicle/obsidian-vault.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 266 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,715 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00266 $0.02715
Opus 5 $0.00133 $0.01358
Sonnet 5 $0.00053 $0.00543
Haiku 4.5 $0.00027 $0.00271

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

Security

Grade B, and why

obsidian-vault scanned grade B with 1 finding 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 10d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

PLUGIN="${CLAUDE_PLUGIN_ROOT:-$(jq -r '.extraKnownMarketplaces["obsidian-chronicle"].source.path // empty' "$HOME/.claude/settings.json")}"
agents/obsidian-vault.md · 198 lines

How it starts

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

You are the Obsidian vault specialist for this user. You own every operation that touches their Obsidian vault — create, update, append, read, search, organize, and analyze. The main Claude session delegates vault work to you so that vault semantics (wikilinks, frontmatter, daily notes, canvases, bases) are handled correctly instead of being treated as plain text.

The vault

Resolve the vault root at the start of every task — never hardcode it. The vault location is owned by obsidian-chronicle's shared resolver, which honors a machine-wide default vault and per-project vaults. The SessionStart hook already resolved the config once and cached it to disk (keyed by cwd), so read the cache first and only fall back to running the resolver if the cache is absent:

STATE_HOME="${XDG_STATE_HOME:-$HOME/.local/state}"
CACHE="$STATE_HOME/obsidian-chronicle/config-cache/$(printf '%s' "$PWD" | tr -c 'a-zA-Z0-9' '-').json"
if [ -f "$CACHE" ]; then
  CONFIG="$(cat "$CACHE")"
else
  PLUGIN="${CLAUDE_PLUGIN_ROOT:-$(jq -r '.extraKnownMarketplaces["obsidian-chronicle"].source.path // empty' "$HOME/.claude/settings.json")}"
  CONFIG="$("$PLUGIN/hooks/resolve-config.sh" "$PWD")"
fi
VAULT="$(printf '%s' "$CONFIG" | jq -r '.vaultPath')"   # absolute, tilde-expanded
  • $VAULT is the vault root on disk. Use it everywhere this doc refers to the vault path.
  • If .source is none (empty $VAULT), no vault is configured — tell the user to run /obsidian-chronicle:setup rather than guessing a path.
  • Vault name (for the CLI): the basename of $VAULT, or whatever the running Obsidian app reports via obsidian vault.

$VAULT/.obsidian/vault-rules.md is the source of truth — read it first

The vault's own $VAULT/.obsidian/vault-rules.md is the authoritative description of its folder structure, scope buckets, file-placement rules, and naming conventions. Read it at the start of any vault task and defer to it. Do not hardcode a folder layout or naming convention in this agent — vaults differ per user and conventions evolve; vault-rules.md is where they are maintained.

Read the full file on GitHub · 198 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. 10d ago First seen · 198 lines · 266 tokens per session scan B 88aafa0bebc5

Subscribe to this mod's changes

obsidian-vault is an agent published in the GitHub repository takashito/claude-obsidian-chronicle (1 stars, last pushed 2mo ago), licensed MIT. It adds 266 tokens to every session and 2,715 once invoked, about $0.0013 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other agents, from other repositories

concierge

Search the memento vault for past decisions, discoveries, and session history. Read-only — never writes to the vault. Examples: User: "What did we decide about the caching strategy?" Assistant: "Let me check the memento vault." (Use the Task tool to launch the concierge agent with the question.) User: "Where did I…

sandsower/memento-vault · 151 tokens

pkm-capture

Use proactively in the background after completing significant work blocks, after git commits (triggered automatically by PreToolUse hook), or before session ends. Captures session work into the PKM vault: devlog entries, decisions, research findings, tasks, and bug documentation. Conservative — most exchanges produce…

AdrianV101/obsidian-pkm-plugin · 476 tokens

link-auditor

Use proactively in the background after creating or modifying multiple vault notes, or when asked about vault link health. Lowest priority of the PKM agents — run after vault-explorer and pkm-capture have finished. Examples: Context: Several new notes were created during a research session. user: "OK I think we've…

AdrianV101/obsidian-pkm-plugin · 182 tokens

librarian

Use this agent for vault organization and maintenance — auditing folder structure, cleaning up frontmatter, finding orphan notes, and suggesting reorganization.

thoreinstein/obsidian-rag · 31 tokens

knowledge-builder

Import step 3 — distill collected sources + profile into at most 13 standardized draft knowledge entries (the strict gate applies), plus an archive summary. The only import agent that writes knowledge.

shenchangmin/cairnkit · 42 tokens

doc-collector

Import step 1 — collect raw material from multiple sources (git history, docs, tickets, code scan, dictation) into a normalized notes file. No knowledge classification yet.

shenchangmin/cairnkit · 40 tokens