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 for Claude Code and Codex by ondrasek/cc-plugins

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

Clone the repo

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

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-setup/github.svg)](https://agentmods.dev/skills/ondrasek/cc-plugins/vault-setup)

Your own site

<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-setup"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/vault-setup"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/vault-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

Model	Per session	Once invoked
Fable 5.1	$0.00076	$0.00948
Opus 5.5	$0.00030	$0.00379
Sonnet 5.5	$0.00015	$0.00190
Haiku 4.5	$0.00008	$0.00095

Measured 1mo ago against content hash 20e2840c5429, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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.

1mo 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 5mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 948 once invoked, about $0.0003 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.

CI and CD DevOps and cloud Testing

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/ruflo · 36 tokens

quality-scan

Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.

diegosouzapw/OmniRoute · 45 tokens

e2e-testing

Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.

thedaviddias/Front-End-Checklist · 38 tokens

test-setup

Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.

Donchitos/Claude-Code-Game-Studios · 32 tokens

mirrord-prev-env

Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…

metalbear-co/mirrord · 122 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 151 tokens