use-ast-factories

use-ast-factories is a cursor rule for Codex from prisma/prisma-next. It costs 0 tokens per session (735 once invoked), scanned A, a copy of use-ast-factories, Apache-2.0.

A testing rule for creating abstract syntax tree (AST) nodes with factory functions instead of assembling their object fields by hand.

In plain words
What is it for?
It helps write tests for code that parses or builds structured source trees, using the project's AST creation helpers.
Why use it?
It reduces missing fields, invalid values, and repeated structure definitions, making AST-related tests easier to update when the structure changes.

Cursor rule for Codex

Install

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.

agentmods
npx agentmods add rules/prisma/prisma-next/use-ast-factories
Clone the repo
git clone --depth 1 https://github.com/prisma/prisma-next

Made for: Codex.

Wrote 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.

agentmods badge for use-ast-factories

README.md
[![agentmods](https://agentmods.dev/badge/rules/prisma/prisma-next/use-ast-factories.svg)](https://agentmods.dev/rules/prisma/prisma-next/use-ast-factories)
Your own site
<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>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 735 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash de62b843716b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

Origin

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.

.agents/rules/use-ast-factories.mdc · 76 lines

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 a ColumnRef
  • createParamRef(index, name?) - Creates a ParamRef
  • createLiteralExpr(value) - Creates a LiteralExpr
  • createTableRef(name) - Creates a TableRef
  • createBinaryExpr(op, left, right) - Creates a BinaryExpr (from ast/predicate)

When to Use Factory Functions

Use factory functions when:

  • ✅ Creating ColumnRef, ParamRef, LiteralExpr, TableRef in tests
  • ✅ Creating BinaryExpr in 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

Read the full file on GitHub · 76 lines

Changes

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.

  1. yesterday First seen · 76 lines · 0 tokens per session scan A de62b843716b

Subscribe to this mod's changes

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.