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.
curl -O https://raw.githubusercontent.com/jjsmackay/obsidian-git-sync-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/jjsmackay/obsidian-git-sync-mcpWrote 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.
[](https://agentmods.dev/instructions/jjsmackay/obsidian-git-sync-mcp/claude-md)<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="Measured on agentmods" height="20"></a>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.00454 | $0.00454 |
| Opus 5 | $0.00227 | $0.00227 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00045 | $0.00045 |
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 7d 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.
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(barepytest/uv run pytestfail — needs the dev extra +python -m) - The two images build via
.github/workflows/build-containers.ymlon push tomain/v*tags →ghcr.io/jjsmackay/obsidian-mcpand…/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:proposeSTOPS at "ready for apply" (generates artifacts, doesn't apply/archive) — continue explicitly. - Per change, two commits directly on
main(not a branch):docs(openspec): propose <slug>, then the impl commit (feat(...)/docs(...)) that folds inopsx:archive(spec sync + move toopenspec/changes/archive/). openspec archivestamps 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 withopenspec init --tools claude.
Gotchas
VAULT_GIT_ENABLED=truemakes 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-mcpis consumed as base image + Python dependency; contribute changes upstream, don't fork.
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.
- 7d ago First seen · 27 lines · 454 tokens per session scan A 6510c06192f2
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 454 tokens to every session, about $0.0023 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.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.