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/bravew/troveWrote 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/bravew/trove/trove-obsidian-bases)<a href="https://agentmods.dev/rules/bravew/trove/trove-obsidian-bases"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-obsidian-bases/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/bravew/trove/trove-obsidian-bases"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-obsidian-bases.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.00880 | $0.00880 |
| Opus 5.5 | $0.00352 | $0.00352 |
| Sonnet 5.5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
trove-obsidian-bases 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 1mo 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian Bases
A .base file is YAML describing views over vault files and their properties.
Creating a view does not require rewriting the source notes.
Workflow
- Read the existing base and representative notes. Establish the scope, property names, types, missing values, and available view plugins.
- Preserve unrelated views, formulas, display settings, and unknown extension fields. Select notes using global filters, then refine individual views.
- Define computed values in
formulas. Reference them asformula.namein view columns and display settings. Note properties usenote.nameor a bare name; file metadata usesfile.name,file.ext, and similar fields. - Use table, cards, or list views supported by the installed app. A map view needs the Maps community plugin; do not install it as a side effect. Use a table fallback if appropriate and explain any unavailable requested view.
- Parse YAML, check filter structure and formula references, and inspect representative results in Obsidian when available. A YAML parser cannot evaluate the formula language. State when runtime evaluation was unavailable.
Read formulas-and-views.md for additional functions, summaries, grouping, and embedding context.
Working example
filters:
and:
- 'file.ext == "md"'
- 'file.inFolder("Projects")'
- 'file.hasTag("task")'
formulas:
days_left: 'if(due, (date(due) - today()).days.round(0), "")'
properties:
formula.days_left:
displayName: Days left
views:
- type: table
name: Active tasks
filters:
and:
- 'status != "done"'
groupBy:
property: status
direction: ASC
order:
- file.name
- status
- due
- formula.days_left
- type: table
name: Completed
filters: 'status == "done"'
order:
- file.name
- status
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.
- 1mo ago First seen · 95 lines · 880 tokens per session scan A a583d7829356
trove-obsidian-bases is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 880 tokens to every session, about $0.0035 per session on Opus 5.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-09-11.
Other cursor rules, from other repositories
sigma-reports
Build, validate, retrieve, and safely update Sigma report code representations through /v2/reports/spec. Use for fixed-layout or pixel-perfect reports, executive board packets, wide operational tables, invoices, statements, regulatory documents, PDF delivery, and bursting one copy per store/account/recipient. Covers…
citazioni
Citazioni corrette (stile numerico) e bibliografia coerente per tesi triennale in LaTeX.
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.
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.