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/sql-queries-not-astsgit 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/sql-queries-not-asts)<a href="https://agentmods.dev/rules/prisma/orm/sql-queries-not-asts"><img src="https://agentmods.dev/badge/rules/prisma/orm/sql-queries-not-asts.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.00445 | $0.00445 |
| Opus 5 | $0.00222 | $0.00222 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
sql-queries-not-asts 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:
- sql-queries-not-asts — 100% identical, 0 lines differ
What it actually says
In the SQL query surface, the things you build and lower are queries, not "asts"
When you build a node (or a list of nodes) that will be handed to adapter.lower() / family.lowerAst() and executed against the driver, that deliverable is a query. Name methods, functions, variables, and parameters accordingly:
bootstrapControlTableQueries(),bootstrapSignMarkerQueries()— not*Asts.buildControlTableBootstrapQueries(),buildSignMarkerBootstrapQueries()— not*Asts.- Local variables:
const queries = …,for (const query of queries),schemaQuery,tableQueries— notasts/ast/schemaAst/tableAsts.
"AST" is the structural noun for the tree shape (DdlNode, AnyQueryAst, the abstract-syntax-tree machinery, a *Visitor). It is not the name for the unit a caller constructs and executes. A function that returns readonly DdlNode[] for the runner to lower is returning queries, even though each element is a node.
Why
- The codebase's ubiquitous language calls the executed unit a query. Calling collections of them "asts" leaks an implementation noun into surfaces that are about what gets run.
- This is a repeat correction. Defaulting to
*Astsfor builder/return names has been flagged more than once in review; pick the right noun at authoring time.
Quick check before staging
git diff --cached -- '*.ts' | rg '^\+' | rg -i '\bbootstrap\w*Asts\b|\bbuild\w*Asts\b|\b\w+Asts\b\s*\(|\bschemaAst\b|\btableAsts\b'
Output should be empty. Structural names (DdlNode, AnyQueryAst, DdlVisitor, accept) are fine and expected.
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 · 28 lines · 445 tokens per session scan A 321f29374e51
sql-queries-not-asts is a cursor rule published in the GitHub repository prisma/orm (47,601 stars, last pushed 2d ago), licensed Apache-2.0. It adds 445 tokens to every session, about $0.0022 per session on Opus 5. 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
test-database-limitations
Test databases created via withDevDatabase() from @prisma-next/test-utils use pglite (an in-memory PostgreSQL implementation via @prisma/dev). Pglite does not support PostgreSQL extensions like pgvector, pgtrgm, etc.
postgres-lateral-patterns
PostgreSQL LATERAL and jsonagg rendering patterns.
sql-queries-not-asts
Name built-and-lowered SQL units "queries", not "asts".
query-patterns
Standard patterns for working with Prisma Next queries.
storage-type-hooks
Use codec-owned storage-type hooks for control-plane type behavior.
contract-space-package-layout
On-disk layout for packages that expose a contract space (extensions, internal monorepo packages, aggregate-root apps).