docs-sync

Rules for keeping a project's documentation in sync with an Obsidian vault through EVC Local Sync. They define which documentation files to read, update, and protect when project specifications or architecture change.

In plain words
What is it for?
Use them when changing project specifications or architecture, especially when working with the /docs folder and its PRD.md requirements file.
Why use it?
They help keep the project documentation consistent and prevent accidental deletion or changes that conflict with the requirements source of truth.

Cursor rule for Cursor

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 rules/entire-vc/evc-local-sync-plugin/docs-sync
Clone the repo
git clone --depth 1 https://github.com/entire-vc/evc-local-sync-plugin

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 126 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00126
Opus 5 $0.00000 $0.00063
Sonnet 5 $0.00000 $0.00025
Haiku 4.5 $0.00000 $0.00013

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

Security

Grade A, and why

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

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.

starter-pack/.cursor/rules/docs-sync.mdc · 15 lines

What it actually says

Documentation Sync Rules

The /docs folder is bidirectionally synced with an Obsidian vault via EVC Local Sync.

Rules:

  • Read /docs files before making changes to understand current state
  • Update /docs when modifying project specs or architecture
  • Never delete /docs files without explicit user confirmation
  • Reference /docs/PRD.md as the source of truth for requirements
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. 2d ago First seen · 15 lines · 0 tokens per session scan A 0424e5b1c832

Subscribe to this mod's changes

docs-sync is a cursor rule published in the GitHub repository entire-vc/evc-local-sync-plugin (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 126 tokens. 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-30.