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/prisma/orm/capabilities-ownershipgit clone --depth 1 https://github.com/prisma/ormWhat 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.00000 | $0.00127 |
| Opus 5 | $0.00000 | $0.00063 |
| Sonnet 5 | $0.00000 | $0.00025 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
capabilities-ownership 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- capabilities-ownership — 100% identical, 0 lines differ
What it actually says
Capability Ownership
Capabilities describe the database environment and are reported by adapters. The contract only declares required capabilities in contract.capabilities and pins the resulting profileHash.
Do
- Describe capabilities as adapter-reported and negotiated at connect time
- Frame contract capabilities as requirements, not definitions
Avoid
- Wording that implies the contract owns or defines capabilities
- Treating
sql.*as a separate “SQL family” capability set rather than shared adapter keys
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.
- 2d ago First seen · 20 lines · 0 tokens per session scan A 7c989e928d6a
capabilities-ownership is a cursor rule published in the GitHub repository prisma/orm (47,587 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 127 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-30.
Other cursor rules, from other repositories
playwright-e2e
Playwright E2E testing configuration for AI agents.
react-components
Rules for writing React components in this project.
state-management
Rules for Redux state management.
server-patterns
Rules for server-side Express code.
project
AI Phone Agent — TypeScript voice backend (Twilio + Amazon Connect).
typescript-style
TypeScript style — prefer arrow functions and consistent callbacks.