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/databrickslabs/ontobricks/cursorrulesgit clone --depth 1 https://github.com/databrickslabs/ontobricksWhat 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.00981 | $0.00981 |
| Opus 5 | $0.00491 | $0.00491 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
cursorrules 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.
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.
- yesterday First seen · 60 lines · 981 tokens per session scan A 69d5de8eef1b
cursorrules is a cursor rule published in the GitHub repository databrickslabs/ontobricks (298 stars, last pushed 3d ago), with no licence file. It adds 981 tokens to every session, about $0.0049 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-30.
Other cursor rules, from other repositories
dkg-annotate
Annotate every substantive chat turn into the DKG project's sub-graphs via the V10 MCP tools (knowledgeassetcreate → write → share) so shared project memory grows organically and stays navigable, with every annotation linked back to its chat:Turn by the predicted turn URI.
mermaid-diagram-preset
Mermaid sequence diagram preset for all Markdown docs in this repo. Gives rectangles and notes enough breathing room that they don't overlap the arrows around them.
rust-coding-style
Cursor rule "rust-coding-style" from hashintel/hash, covering rust coding style, project-specific patterns, type system, async patterns and function arguments.
rust-testing-strategy
Cursor rule "rust-testing-strategy" from hashintel/hash, covering rust testing strategy, verification commands, test execution, test design principles and assertion standards.
typescript-coding-guidelines
TypeScript coding guidelines / style – check when working on TypeScript files.
meaningful-identifiers
Naming guidance for callback parameters and local variables in TypeScript. Use when writing or refactoring loops, array callbacks (map/filter/find/reduce), or local accumulators.