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/dkdottk/obsidian-bridge/vault-safetygit clone --depth 1 https://github.com/dkdottk/obsidian-bridgeWrote 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/dkdottk/obsidian-bridge/vault-safety)<a href="https://agentmods.dev/rules/dkdottk/obsidian-bridge/vault-safety"><img src="https://agentmods.dev/badge/rules/dkdottk/obsidian-bridge/vault-safety.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.00137 | $0.00137 |
| Opus 5 | $0.00068 | $0.00068 |
| Sonnet 5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
vault-safety 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 4d 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
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 4d ago First seen · 14 lines · 137 tokens per session scan A a36cf60ec89c
vault-safety is a cursor rule published in the GitHub repository dkdottk/obsidian-bridge (1 stars, last pushed 28d ago), licensed AGPL-3.0. It adds 137 tokens to every session, about $0.0007 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
lians-memory
Current Lians task, control policy, and bounded context.
cursor-brain-os
Brain OS operating instructions — use MCP tools for project state, not source-code grep.
ctxfile
You have access to the ctxfile MCP tools (getcontext, savesession, continuethread, listthreads, ingestcontext). These behaviors make context capture automatic. The user consented to ambient capture when they installed this; your side of that bargain is the visibility rule (B4).
loredex
Route research and findings through loredex instead of ad-hoc summary files.
swap-asset-resolution
Resolve IronWallet swap assets from catalog tools, not memory.
joplin-brain-config
joplin-llm-wiki 設定與測試中的 knowledge flow／notebook export／agent compile／joplinwikiwriteback 慣例.