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/prisma-next/control-plane-descriptorsgit clone --depth 1 https://github.com/prisma/prisma-nextWhat 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.01125 |
| Opus 5 | $0.00000 | $0.00562 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
control-plane-descriptors 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.
This is a copy
92% identical to control-plane-descriptors — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Control Plane Descriptors Pattern
Overview
Control plane components (families, targets, adapters, drivers, extensions) use a consistent descriptor + instance pattern defined in ADR 151. All legacy descriptor types have been removed and replaced with Control*Descriptor types.
Pattern: ControlDescriptor + ControlInstance
CRITICAL: Always use Control*Descriptor types. Legacy types (FamilyDescriptor, TargetDescriptor, AdapterDescriptor, DriverDescriptor, ExtensionDescriptor, ControlPlaneDriver) have been completely removed.
Descriptor Types
All control plane descriptors follow this pattern:
// Family descriptor
ControlFamilyDescriptor<TFamilyId, TFamilyInstance>
// Target descriptor
ControlTargetDescriptor<TFamilyId, TTargetId, TTargetInstance>
// Adapter descriptor
ControlAdapterDescriptor<TFamilyId, TTargetId, TAdapterInstance>
// Driver descriptor
ControlDriverDescriptor<TFamilyId, TTargetId, TDriverInstance>
// Extension descriptor
ControlExtensionDescriptor<TFamilyId, TTargetId, TExtensionInstance>
Required Properties
All descriptors must have:
kind: Discriminator ('family' | 'target' | 'adapter' | 'driver' | 'extension')id: String identifierfamilyId: Literal type (e.g.,'sql')targetId: Literal type (e.g.,'postgres') - required for target, adapter, driver, extensionmanifest:ExtensionPackManifestcreate(): Factory method that returns an instance
Instance Types
Base instance interfaces:
ControlFamilyInstance<TFamilyId>ControlTargetInstance<TFamilyId, TTargetId>ControlAdapterInstance<TFamilyId, TTargetId>ControlDriverInstance<TTargetId>(replacesControlPlaneDriver)ControlExtensionInstance<TFamilyId, TTargetId>
Note: FamilyInstance is retained for CLI command handlers that need the full method set (validateContractIR, verify, schemaVerify, introspect, emitContract, toSchemaView). It uses ControlDriverInstance internally.
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 · 128 lines · 0 tokens per session scan A b6b5d1f1458e
control-plane-descriptors is a cursor rule published in the GitHub repository prisma/prisma-next (420 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,125 tokens. A static security scan graded it A with 0 findings. It is 92% identical to control-plane-descriptors, differing in 22 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.