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.
npx agentmods add rules/michele-prandina/claude2e/vault-syncgit clone --depth 1 https://github.com/michele-prandina/ClaudE2EWrote 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/rules/michele-prandina/claude2e/vault-sync)<a href="https://agentmods.dev/rules/michele-prandina/claude2e/vault-sync"><img src="https://agentmods.dev/badge/rules/michele-prandina/claude2e/vault-sync.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 | $0.00282 | $0.00282 |
| Opus 5 | $0.00141 | $0.00141 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
vault-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 5d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 5d ago First seen · 27 lines · 282 tokens per session scan A 02f570bf3a0a
vault-sync is a cursor rule published in the GitHub repository michele-prandina/ClaudE2E (8 stars, last pushed 6mo ago), with no licence file. It adds 282 tokens to every session, about $0.0014 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 cursor rules, from other repositories
cursorrules
Universal Long-Term Memory & Cross-Agent Handoff Protocol for AI Coding Agents.
archcore-context
Archcore knowledge base context — document types, MCP tools, and conventions for working with .archcore/ documents.
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
context-management
Context window management — prevents AI from losing track during long sessions.
react-best-practices
USE WHEN: Designing React components, implementing hooks, and managing component lifecycles.
search-routing
Smart Search Routing — always use QMD semantic search when available, never bypass with grep for vault content.