obsidian-rag: Instructions file for Claude Code

CLAUDE.md

obsidian-rag CLAUDE.md is an instructions file for Claude Code from thoreinstein/obsidian-rag. It costs 677 tokens per session, scanned A, original, MIT.

Project instructions for obsidian-rag, a Claude Code plugin that connects an Obsidian note vault to a local search system. They describe its design, build process, file paths, and dependency rules.

In plain words
What is it for?
Use them when developing, building, or debugging obsidian-rag, especially its MCP tools, note indexing, vector storage, and embedding setup.
Why use it?
They give coding agents the project context and constraints needed to change or build obsidian-rag without breaking its local search or native dependencies.

Instructions file for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_DATA} variable. Also seen: mentions .claude-plugin; mentions Claude Code.

This is thoreinstein/obsidian-rag's own configuration. It tells Claude Code how to work on obsidian-rag itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything obsidian-rag configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thoreinstein/obsidian-rag. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/thoreinstein/obsidian-rag/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/thoreinstein/obsidian-rag

Made for: Claude Code.

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-rag CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thoreinstein/obsidian-rag/claude-md/github.svg)](https://agentmods.dev/instructions/thoreinstein/obsidian-rag/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/thoreinstein/obsidian-rag/claude-md"><img src="https://agentmods.dev/badge/instructions/thoreinstein/obsidian-rag/claude-md/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-rag CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/thoreinstein/obsidian-rag/claude-md"><img src="https://agentmods.dev/badge/instructions/thoreinstein/obsidian-rag/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 677 This file is loaded in full into every session.
When invoked 677 The same file — it is already loaded in full.
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.00677 $0.00677
Opus 5.5 $0.00271 $0.00271
Sonnet 5.5 $0.00135 $0.00135
Haiku 4.5 $0.00068 $0.00068

Measured 1mo ago against content hash dbd382929f91, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

obsidian-rag CLAUDE.md 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 1mo 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.

CLAUDE.md · 52 lines

How it starts

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

obsidian-rag

Claude Code plugin providing Obsidian vault integration with local RAG (Retrieval Augmented Generation).

Architecture

  • MCP Server (src/index.ts): Exposes 16 tools via the Model Context Protocol over stdio. Also supports one-shot CLI mode for hook scripts.
  • Embedder (src/rag/embedder.ts): Local embedding via @xenova/transformers (all-MiniLM-L6-v2). Singleton pattern.
  • Vector Store (src/rag/store.ts): LanceDB-backed vector store with incremental indexing and md5-based change detection.

Build

npm install
npm run build

The build uses esbuild to bundle into dist/index.js (committed to the repo). Native dependencies (@lancedb/lancedb, onnxruntime-node, sharp) are externalized.

Key Constraints

  • onnxruntime-node pinned to 1.14.0: Required by @xenova/transformers 2.17.x. Do not upgrade.
  • Native deps externalized: The esbuild bundle excludes @lancedb/lancedb, onnxruntime-node, and sharp — they load from node_modules at runtime.
  • sharp is required: Transitive runtime dependency of @xenova/transformers (imported at top-level in utils/image.js). Must stay in dependencies since esbuild externalizes it.
  • Dependency placement is intentional: Bundled deps (MCP SDK, transformers, glob, gray-matter, md5) are in devDependencies because esbuild bakes them into dist/index.js. Externalized native deps are in dependencies because they load from node_modules at runtime.
  • dist/ is committed: The built artifact is checked in so the plugin works without a build step after clone + npm install.

Data Paths

When running as an installed plugin, all state is stored in ${CLAUDE_PLUGIN_DATA}/ (persistent across plugin updates). Falls back to ~/ for development/CLI usage.

  • Config: .obsidian-rag.config.json
  • LanceDB: .obsidian-rag-lancedb/
  • File hashes: .obsidian-rag-file-hashes.json

Environment Variables

  • OBSIDIAN_VAULT_PATH: Default vault path (overrides config file)
  • OBSIDIAN_RAG_MIN_CHUNK_CHARS: Minimum chunk size (default 40)
  • OBSIDIAN_RAG_MAX_CHUNK_CHARS: Maximum chunk size (default 1800)
  • OBSIDIAN_RAG_TARGET_CHUNK_CHARS: Target chunk size for merging (default 700)
  • OBSIDIAN_RAG_EMBED_BATCH_SIZE: Embedding batch size (default 48)

Read the full file on GitHub · 52 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. 1mo ago First seen · 52 lines · 677 tokens per session scan A dbd382929f91

Subscribe to this mod's changes

obsidian-rag CLAUDE.md is an instructions file published in the GitHub repository thoreinstein/obsidian-rag (2 stars, last pushed 2mo ago), licensed MIT. It adds 677 tokens to every session, about $0.0027 per session on Opus 5.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-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens