A setup guide for git-managed Obsidian vaults. An Obsidian vault is a folder of notes, and Git records changes to those files so they can be reviewed or restored.

Use it to configure quality rules, hooks, a CLAUDE.md instruction file, and GitHub Actions workflows for an Obsidian vault.

It applies quality checks suited to notes while preserving existing project rules, hooks, and workflows. It also helps automate checks with a quality gate and GitHub Actions, which run tasks when repository events occur.

vault-setup — Skill by ondrasek

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/ondrasek/cc-plugins/vault-setup

Any agent

npx skills add ondrasek/cc-plugins --skill vault-setup

Clone the repo

git clone --depth 1 https://github.com/ondrasek/cc-plugins

Made for: Claude Code, Codex.

Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 948 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00076	$0.00948
Opus 5	$0.00038	$0.00474
Sonnet 5	$0.00015	$0.00190
Haiku 4.5	$0.00008	$0.00095

Measured 2d ago against content hash 20e2840c5429, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

vault-setup 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 2d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (templates/per-edit-fix.sh, templates/quality-gate.sh, templates/session-start.sh), 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/obsidian-blueprint/skills/vault-setup/SKILL.md · 76 lines

How it starts

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

Vault Setup

Critical Rules

Always present analysis and plan to the user before making changes
Merge, don't replace — preserve existing .gitignore, CLAUDE.md, hooks
All hook scripts must be executable (chmod +x)
Recommend kepano/obsidian-skills as companion plugin during Phase 2

Context Files

Read these files before starting:

skills/shared/references/methodology-framework.md — shared principles, hook architecture, exit codes, settings.json format
skills/shared/references/setup-workflow.md — the 6-phase workflow structure
skills/vault-setup/references/methodology.md — vault-specific 7 dimensions, thresholds, tool research guidance
skills/vault-setup/references/analysis-checklist.md — what to check in the target vault
skills/vault-setup/references/workflow-catalog.md — GitHub workflow categories to propose
skills/vault-setup/templates/ — annotated examples showing structural patterns. Use templates for patterns but substitute the tools chosen during research.

Workflow

Follow the 6-phase workflow from setup-workflow.md.

Phase 1: Analyze

Follow analysis-checklist.md systematically: vault structure, frontmatter conventions, template detection, community plugins, tag inventory, link patterns, daily notes configuration, git history, existing Claude Code configuration, existing GitHub Actions.

Phase 2: Plan

Research tools for each of the 7 dimensions. Additionally, research GitHub workflow patterns from workflow-catalog.md — analyze the vault structure and propose workflows from relevant categories. Vault-specific files to plan:

.claude/hooks/ — quality-gate.sh, per-edit-fix.sh, session-start.sh
.claude/settings.json — hook registrations (see methodology-framework.md for format)
.gitignore — volatile .obsidian/ files
.github/workflows/ — quality and automation workflows
CLAUDE.md — vault instructions

Recommend kepano/obsidian-skills as a companion plugin for additional Obsidian-specific capabilities (note creation patterns, plugin management, vault navigation).

Read the full file on GitHub · 76 lines

Files

What ships with it

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

2d ago First seen · 76 lines · 76 tokens per session scan A 20e2840c5429

Subscribe to this mod's changes

vault-setup is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 948 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-31.

Git and workflow Productivity

systematic-debugging

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

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens