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-json-canvas)<a href="https://agentmods.dev/rules/bravew/trove/trove-json-canvas"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-json-canvas/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-json-canvas"><img src="https://agentmods.dev/badge/rules/bravew/trove/trove-json-canvas.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.01027 | $0.01027 |
| Opus 5 | $0.00513 | $0.00513 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
trove-json-canvas 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 yesterday.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JSON Canvas
Use JSON Canvas 1.0 for a requested .canvas artifact. It is a portable file
format and can be authored without Obsidian. Do not substitute it for another
visual format the user requested.
Workflow
- Read and parse an existing canvas before editing it. For a new canvas,
start with
{"nodes": [], "edges": []}. Both arrays are optional in the specification; include them in newly created files for clarity. - Preserve existing IDs, unknown extension fields, unrelated content, and node order. IDs are unique strings; hexadecimal is an optional generation convention, not a validity requirement. Never rewrite valid IDs for style.
- Position nodes with readable spacing, then connect known node IDs. Keep
groups before their members in the array so the background appears below
the content. Groups contain nodes geometrically, not through a
childrenproperty. Avoid unrelated layout changes when making a focused edit. - Validate JSON and the integrity checks below. Inspect the board in a compatible viewer when available; otherwise identify the visual check as unverified. A request to review or diagnose does not authorize rewriting.
Schema essentials
Every node has string id and type, and integer x, y, width, height.
Use positive dimensions for readable nodes. Coordinates may be negative.
| Node type | Additional fields |
|---|---|
text |
Required string text, which may contain Markdown |
file |
Required string file; optional string subpath starting with # |
link |
Required string url |
group |
Optional string label, string background, and backgroundStyle |
backgroundStyle is cover, ratio, or repeat. Optional color is a hex
color string such as "#FF0000" or a string preset "1" through "6".
Use vault-relative file paths for Obsidian; otherwise follow the target app's
path conventions. Check referenced local files without fetching link nodes.
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.
- yesterday First seen · 94 lines · 1,027 tokens per session scan A 250f127a707a
trove-json-canvas is a cursor rule published in the GitHub repository bravew/trove (10 stars, last pushed yesterday), licensed MIT. It adds 1,027 tokens to every session, about $0.0051 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-09-11.
Other cursor rules, from other repositories
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.
mermaid
Diagram Creator. Load when the user requests "Create a diagram".