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.
git clone --depth 1 https://github.com/beettlle/pi-spineWrote 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/beettlle/pi-spine/obsidian-vault-standards)<a href="https://agentmods.dev/rules/beettlle/pi-spine/obsidian-vault-standards"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/obsidian-vault-standards/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.
<a href="https://agentmods.dev/rules/beettlle/pi-spine/obsidian-vault-standards"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/obsidian-vault-standards.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01604 |
| Opus 5 | $0.00000 | $0.00802 |
| Sonnet 5 | $0.00000 | $0.00321 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
obsidian-vault-standards 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: Obsidian Vault Editor
- Role: PKM and vault artifact editor. Philosophy: Official syntax over invention; wikilinks for internal graph; validate structured files.
- Scope: User mentions Obsidian/vault,
.obsidian/in path, or.base/.canvasedits. Repo docs:documentation-policy.mdc.
Universal: general-llm-anti-patterns.mdc | Syntax: obsidian-skills — npx skills add https://github.com/kepano/obsidian-skills. CLI: obsidian-integration.mdc.
1.1 OFM Syntax Hallucination (CRIT)
CRITICAL: Do not invent callout types, properties, or Obsidian-only syntax.
❌ Bad: > [!custom-ai-type] or unverified YAML keys
✅ Good: Documented callouts (note, warning); verify OFM
⚠️ Why: Invalid syntax breaks reading view and link graph
🔧 Fix: obsidian-markdown skill or official docs
📍 See: general-llm-anti-patterns.mdc section 4.1
Detect: Invented callout types, unverified frontmatter, "Obsidian supports X" without citation
1.2 Internal Link Style (CRIT)
CRITICAL: Wikilinks for vault notes; Markdown links for external URLs only.
❌ Bad: [Meeting](folder/Meeting Notes.md) for vault notes
✅ Good: [[Meeting Notes]], [[Note#Heading]]; [text](https://...) external
⚠️ Why: Path links break on rename; wikilinks are the graph primitive
🔧 Fix: Replace internal [](*.md) with [[wikilinks]]
📍 See: general-llm-anti-patterns.mdc section 4.3
Detect: .md in []() for vault notes, missing [[ for internal refs
1.3 Block ID Placement (CRIT)
CRITICAL: Place ^block-id where Obsidian can anchor block refs.
❌ Bad: ^id inside blockquote/list line incorrectly
✅ Good: ^id on paragraph; separate line after quotes/lists
⚠️ Why: Broken [[Note#^id]] and embeds
🔧 Fix: obsidian-markdown skill block-ID rules
📍 See: general-llm-anti-patterns.mdc section 3.6c
Detect: ^id mid-blockquote, duplicate ^id, ref to missing block
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.
- 10d ago First seen · 132 lines · 0 tokens per session scan A 069872a4fabf
obsidian-vault-standards is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,604 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.