Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.
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/use-hash-constructorsgit clone --depth 1 https://github.com/prisma/ormWrote 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/orm/use-hash-constructors)<a href="https://agentmods.dev/rules/prisma/orm/use-hash-constructors"><img src="https://agentmods.dev/badge/rules/prisma/orm/use-hash-constructors.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.00419 |
| Opus 5 | $0.00000 | $0.00210 |
| Sonnet 5 | $0.00000 | $0.00084 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
use-hash-constructors 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- use-hash-constructors — 94% identical, 6 lines differ
What it actually says
Use Hash Constructors for Branded Hash Types
When creating CoreHashBase or ProfileHashBase values in tests, use the coreHash() and profileHash() constructors from @internal/contract/types.
The Problem
CoreHashBase and ProfileHashBase are branded types (string & Brand<'CoreHash'>). Plain strings don't satisfy the brand, so tests historically used as never casts to bypass the type system:
// ❌ WRONG: unsafe cast, hides the branded type from the reader
coreHash: 'test' as never,
profileHash: 'test-profile' as never,
The Solution
import { coreHash, profileHash } from '@internal/contract/types';
// ✅ CORRECT: type-safe, preserves literal type via const type parameter
coreHash: coreHash('test'),
profileHash: profileHash('test-profile'),
The constructors use const type parameters so coreHash('test') returns CoreHashBase<'test'>, not CoreHashBase<string>.
Available Constructors
From @internal/contract/types:
coreHash<const T extends string>(value: T): CoreHashBase<T>profileHash<const T extends string>(value: T): ProfileHashBase<T>
When to Use
- ✅ Any test or test utility that constructs an
SqlContractorContractBaseliteral - ✅ Test helper functions that accept optional hash strings and need to produce branded values
Do not use these in production emission code — the emitter computes hashes via computeCoreHash() and returns plain strings that are consumed at the type level through contract.d.ts.
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 · 45 lines · 0 tokens per session scan A 1711d2a44ec6
use-hash-constructors is a cursor rule published in the GitHub repository prisma/orm (47,601 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 419 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-09-03.
Other cursor rules, from other repositories
config-validation-and-normalization
Patterns for config validation and normalization using Arktype.
contract-space-package-layout
On-disk layout for packages that expose a contract space (extensions, internal monorepo packages, aggregate-root apps).
sql-types-imports
Canonical import paths for SQL types.
cli-package-exports
CLI package export patterns and import conventions.
resolving-cyclic-dependencies
How to resolve cyclic dependencies when moving types or refactoring packages.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values. Enforced by lint:framework-vocabulary.