control-plane-descriptors

A descriptor-and-instance pattern for control-plane components such as families, targets, adapters, drivers, and extensions. A descriptor defines a component's type and identifiers, while its instance provides the implementation.

In plain words
What is it for?
Use it when defining or consuming control-plane families, targets, adapters, drivers, or extensions with the required Control*Descriptor types.
Why use it?
It keeps related control-plane components described in one consistent way and prevents use of removed legacy descriptor types.

Cursor rule for Codex

Install

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.

agentmods
npx agentmods add rules/prisma/orm/control-plane-descriptors
Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Codex.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,104 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01104
Opus 5 $0.00000 $0.00552
Sonnet 5 $0.00000 $0.00221
Haiku 4.5 $0.00000 $0.00110

Measured 2d ago against content hash db31cb4aa228, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/rules/control-plane-descriptors.mdc · 128 lines

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 identifier
  • familyId: Literal type (e.g., 'sql')
  • targetId: Literal type (e.g., 'postgres') - required for target, adapter, driver, extension
  • manifest: ExtensionPackManifest
  • create(): Factory method that returns an instance

Instance Types

Base instance interfaces:

  • ControlFamilyInstance<TFamilyId>
  • ControlTargetInstance<TFamilyId, TTargetId>
  • ControlAdapterInstance<TFamilyId, TTargetId>
  • ControlDriverInstance<TTargetId> (replaces ControlPlaneDriver)
  • 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.

Read the full file on GitHub · 128 lines

Changes

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.

  1. 2d ago First seen · 128 lines · 0 tokens per session scan A db31cb4aa228

Subscribe to this mod's changes

control-plane-descriptors 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 1,104 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.