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.
git 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/sql-queries-not-asts)<a href="https://agentmods.dev/rules/prisma/prisma-next/sql-queries-not-asts"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/sql-queries-not-asts/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/prisma/prisma-next/sql-queries-not-asts"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/sql-queries-not-asts.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00445 | $0.00445 |
| Opus 5.5 | $0.00178 | $0.00178 |
| Sonnet 5.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 1mo 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 sql-queries-not-asts — 0 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.
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.
- 1mo ago 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/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 445 tokens to every session, about $0.0018 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to sql-queries-not-asts, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
sql-queries-not-asts
Name built-and-lowered SQL units "queries", not "asts".
supabase
Do not use the Supabase Client, instead use the Jawn Client and put all new endpoints in controllers. Don't use RLS policies, instead enable RLS for new tables and revoke privledges. Example.
java-springboot-jpa-cursorrules-prompt-file
Cursor rules for Java development with Springboot and JPA integration.
windsurfrules
Node.js ESM + EloquentJS ORM + PostgreSQL/MongoDB + Express/Fastify.
fastapi-database-interaction
A set of rules for connecting FastAPI, a Python framework for building web APIs, to databases using asynchronous libraries such as asyncpg or aiomysql and SQLAlchemy 2.0.
background-work
Background work on the backend, cron jobs in the scheduler vs tasks in the Postgres queue, transactional enqueue, retries, idempotent handlers.