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/family-instance-domain-actionsgit clone --depth 1 https://github.com/prisma/prisma-nextWrote 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/prisma/prisma-next/family-instance-domain-actions)<a href="https://agentmods.dev/rules/prisma/prisma-next/family-instance-domain-actions"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/family-instance-domain-actions.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01127 |
| Opus 5 | $0.00000 | $0.00563 |
| Sonnet 5 | $0.00000 | $0.00225 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
family-instance-domain-actions 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 4d 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
100% identical to family-instance-domain-actions — 6 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Family Instance Domain Actions
See also: ADR 204 — Domain actions vs composable primitives in the control plane. ADR 204 establishes the broader principle this rule applies inside family instances: action methods compose primitives; compound actions never call peer actions.
Overview
Family instances implement control-plane domain actions (emitContract, verify, schemaVerify, sign) and expose composable primitives (introspect, readMarker, validateContract) as methods. Distinguish them by return shape: actions return CLI/audit envelopes (...Result types with summary, code, meta, timings); primitives return raw data. Both should be self-contained and own their implementation logic.
Pattern: Inline Core Logic, Import Helper Functions
When implementing domain actions on family instances:
✅ CORRECT: Import helper functions, inline orchestration logic
// Import pure helper functions from core
import { canonicalizeContract } from '@prisma-next/core-control-plane/emission/canonicalization';
import { computeExecutionHash, computeProfileHash, computeStorageHash } from '@prisma-next/core-control-plane/emission/hashing';
import { format } from 'prettier';
// Inline the domain action orchestration
async emitContract({ contractIR }): Promise<EmitContractResult> {
const ir = contractIR as ContractIR;
// Validate structure
// ... validation logic ...
// Use helper functions
const storageHash = computeStorageHash(contractJson);
const executionHash = computeExecutionHash(contractJson);
const profileHash = computeProfileHash(contractJson);
const contractJsonString = JSON.stringify(
{ ...JSON.parse(canonicalizeContract(contractWithHashes)), _generated: {...} },
null,
2
);
// Generate types via hook
const contractDts = await format(
sqlTargetFamilyHook.generateContractTypes(ir, codecTypeImports, operationTypeImports),
{ parser: 'typescript', ... }
);
return { contractJson: contractJsonString, contractDts, storageHash, executionHash, profileHash };
}
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.
- 4d ago First seen · 111 lines · 0 tokens per session scan A 6015d7043471
family-instance-domain-actions is a cursor rule published in the GitHub repository prisma/prisma-next (419 stars, last pushed 10d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,127 tokens. A static security scan graded it A with 0 findings. It is 100% identical to family-instance-domain-actions, differing in 6 lines, and is treated as a copy.
Other cursor rules, from other repositories
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
import-validation
Import validation and package layering rules.
no-target-branches
Never branch on target - use adapters instead.