obsidian-git-sync-mcp: Instructions file for Claude Code

CLAUDE.md

obsidian-git-sync-mcp CLAUDE.md is an instructions file for Claude Code from jjsmackay/obsidian-git-sync-mcp. It costs 523 tokens per session, scanned A, original, MIT.

Repository instructions for the Obsidian Git Sync MCP project, covering its commands, change process, testing, deployment, and known details. It is guidance for Claude Code working in that repository, not a general-purpose integration.

In plain words
What is it for?
Following the repository’s test command, preparing changes through its OpenSpec process, understanding container builds, and avoiding documented project mistakes.
Why use it?
It gives an agent the project-specific rules needed to make changes safely and run the correct tests and workflow.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md.

This is jjsmackay/obsidian-git-sync-mcp's own configuration. It tells Claude Code how to work on obsidian-git-sync-mcp 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-git-sync-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jjsmackay/obsidian-git-sync-mcp. 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/jjsmackay/obsidian-git-sync-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/jjsmackay/obsidian-git-sync-mcp

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-git-sync-mcp CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jjsmackay/obsidian-git-sync-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/jjsmackay/obsidian-git-sync-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 523 This file is loaded in full into every session.
When invoked 523 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.00523 $0.00523
Opus 5.5 $0.00209 $0.00209
Sonnet 5.5 $0.00105 $0.00105
Haiku 4.5 $0.00052 $0.00052

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

Security

Grade A, and why

obsidian-git-sync-mcp 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 · 30 lines

What it actually says

CLAUDE.md

Operational notes for this repo. Project thesis, tech stack, and deployment live in openspec/config.yaml (context block) and README.md — don't duplicate them here.

Commands

  • Test: uv run --extra dev python -m pytest (bare pytest / uv run pytest fail — needs the dev extra + python -m)
  • The two images build via .github/workflows/build-containers.yml on push to main/v* tags → ghcr.io/jjsmackay/obsidian-mcp and …/obsidian-sync.

Change workflow

  • Spec-driven via OpenSpec: propose changes with /opsx:propose, not ad-hoc edits.
  • Full cycle: /opsx:propose → commit → /opsx:apply → /opsx:archive → commit. /opsx:propose STOPS at "ready for apply" (generates artifacts, doesn't apply/archive) — continue explicitly.
  • Branch → PR → squash-merge. Never commit directly to main. One branch per change, named <slug>. On it, two commits: docs(openspec): propose <slug>, then the impl commit (feat(...)/docs(...)) that folds in opsx:archive (spec sync + move to openspec/changes/archive/).
  • The squash commit is what lands on main: title it like the impl commit (conventional-commit form), body summarising the why. Open the PR with gh pr create; merge with gh pr merge --squash.
  • openspec archive stamps the archive dir with the host clock (often a day off) — rename the dir to the real date to match siblings.
  • Validator quirk: only a requirement's first line is checked for SHALL/MUST; no backticks in requirement headers.
  • .claude/ is gitignored; regenerate slash commands with openspec init --tools claude.

Gotchas

  • VAULT_GIT_ENABLED=true makes the mcp container fail-closed at startup if the vault isn't a git working tree or the remote is missing (config.py:validate_gitsync).
  • obsidian-web-mcp is consumed as base image + Python dependency; contribute changes upstream, don't fork.
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 Changed · +3 lines · +69 tokens per session 3c995f1d7be4
  2. 2mo ago First seen · 27 lines · 454 tokens per session scan A 6510c06192f2

Subscribe to this mod's changes

obsidian-git-sync-mcp CLAUDE.md is an instructions file published in the GitHub repository jjsmackay/obsidian-git-sync-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 523 tokens to every session, about $0.0021 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

obsidian-git-sync-mcp CLAUDE.md compared with instructions from other repositories

obsidian-git-sync-mcp CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
obsidian-git-sync-mcp CLAUDE.mdjjsmackay/obsidian-git-sync-mcpInstructions file01mo agoMITA523Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k2d agoMITA4,313Codex, OpenCode