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/use-ast-factoriesgit 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/use-ast-factories)<a href="https://agentmods.dev/rules/prisma/prisma-next/use-ast-factories"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/use-ast-factories.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.00735 |
| Opus 5 | $0.00000 | $0.00367 |
| Sonnet 5 | $0.00000 | $0.00147 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
use-ast-factories 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.
This is a copy
100% identical to use-ast-factories — 4 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use Factory Functions for AST Nodes
CRITICAL: When creating AST nodes in tests, use factory functions instead of manual object creation.
The Problem
Manual AST node creation:
- Duplicates AST structure definitions
- Is error-prone (easy to miss required fields or use wrong values)
- Makes refactoring harder (changes to AST structure require updates in many places)
- Doesn't benefit from factory function validation
The Solution
❌ WRONG: Manual AST node creation
const colRef: ColumnRef = { kind: 'col', table: 'user', column: 'id' };
const paramRef: ParamRef = { kind: 'param', index: 1, name: 'userId' };
const literalExpr: LiteralExpr = { kind: 'literal', value: 'test' };
✅ CORRECT: Use factory functions
import { createColumnRef, createParamRef, createLiteralExpr } from '@prisma-next/sql-relational-core/ast';
const colRef: ColumnRef = createColumnRef('user', 'id');
const paramRef: ParamRef = createParamRef(1, 'userId');
const literalExpr: LiteralExpr = createLiteralExpr('test');
Available Factory Functions
From @prisma-next/sql-relational-core/ast:
createColumnRef(table, column)- Creates aColumnRefcreateParamRef(index, name?)- Creates aParamRefcreateLiteralExpr(value)- Creates aLiteralExprcreateTableRef(name)- Creates aTableRefcreateBinaryExpr(op, left, right)- Creates aBinaryExpr(fromast/predicate)
When to Use Factory Functions
Use factory functions when:
- ✅ Creating
ColumnRef,ParamRef,LiteralExpr,TableRefin tests - ✅ Creating
BinaryExprin tests - ✅ Any AST node that has a factory function available
Exception: OperationExpr objects are complex and don't have a factory function (the createOperationExpr function just returns the operation as-is). Manual creation is acceptable for OperationExpr in tests.
Benefits
- Consistency: All AST nodes created the same way
- Type safety: Factory functions ensure correct structure
- Maintainability: Changes to AST structure only need updates in factory functions
- Less duplication: No need to repeat AST structure in tests
- Validation: Factory functions can validate inputs
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 · 76 lines · 0 tokens per session scan A de62b843716b
use-ast-factories 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 735 tokens. A static security scan graded it A with 0 findings. It is 100% identical to use-ast-factories, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
sql-types-imports
Canonical import paths for SQL types.
use-ast-factories
Use factory functions for creating AST nodes instead of manual object creation.
type-extraction-from-contract
Extract TypeScript types from contract.d.ts and helpers.
required-key-undefined-fields
Internal input types use required keys typed | undefined, not optional keys.
type-predicates
Replace blind casts with type predicates (type guards).
use-if-defined
Use ifDefined() for conditional object spreads.