use-if-defined

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

A TypeScript coding rule that uses ifDefined() to add object properties only when their values are not undefined.

In plain words
What is it for?
Use it when building configuration objects or other objects with optional fields.
Why use it?
It makes optional properties explicit and keeps valid falsy values such as 0, empty strings, false, and null.

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-if-defined
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-if-defined

README.md
[![agentmods](https://agentmods.dev/badge/rules/prisma/prisma-next/use-if-defined.svg)](https://agentmods.dev/rules/prisma/prisma-next/use-if-defined)
Your own site
<a href="https://agentmods.dev/rules/prisma/prisma-next/use-if-defined"><img src="https://agentmods.dev/badge/rules/prisma/prisma-next/use-if-defined.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 311 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 94% 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.00311
Opus 5 $0.00000 $0.00156
Sonnet 5 $0.00000 $0.00062
Haiku 4.5 $0.00000 $0.00031

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

Security

Grade A, and why

use-if-defined 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

94% identical to use-if-defined — 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-if-defined.mdc · 45 lines

What it actually says

Use ifDefined() for Conditional Object Spreads

CRITICAL: Use ifDefined from @prisma-next/utils/defined instead of inline conditional spread patterns.

Why?

  • Cleaner, more readable syntax
  • Explicit about which properties are optional
  • Satisfies exactOptionalPropertyTypes
  • Preserves falsy values (0, '', false, null) — only excludes undefined

Examples

❌ WRONG: Inline conditional spread

const obj = {
  required: 'value',
  ...(options.default ? { default: options.default } : {}),
  ...(options.name !== undefined ? { name: options.name } : {}),
};

✅ CORRECT: Using ifDefined

import { ifDefined } from '@prisma-next/utils/defined';

const obj = {
  required: 'value',
  ...ifDefined('default', options.default),
  ...ifDefined('name', options.name),
};

Behavior

  • ifDefined('key', value) returns { key: value } when value !== undefined
  • ifDefined('key', undefined) returns {}
  • Falsy values like 0, '', false, and null are preserved
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 · 45 lines · 0 tokens per session scan A 74355c228ec5

Subscribe to this mod's changes

use-if-defined 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 311 tokens. A static security scan graded it A with 0 findings. It is 94% identical to use-if-defined, differing in 4 lines, and is treated as a copy.