object-hasown

A JavaScript rule for checking whether an object directly contains a property with the modern Object.hasOwn() method. It replaces the older hasOwnProperty() call.

In plain words
What is it for?
Use it whenever code needs to test for an object's own property, including optional nested data. Provide an empty-object fallback when the value might be missing.
Why use it?
The older method can be shadowed or overridden by an object. Object.hasOwn() is safer and works consistently with objects that have unusual prototypes.

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/orm/object-hasown
Clone the repo
git clone --depth 1 https://github.com/prisma/orm

Made for: Codex.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 301 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.00301
Opus 5 $0.00000 $0.00151
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

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

Security

Grade A, and why

object-hasown 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

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/rules/object-hasown.mdc · 39 lines

What it actually says

Use Object.hasOwn() Instead of hasOwnProperty()

CRITICAL: Always use Object.hasOwn() instead of hasOwnProperty() to check for own properties.

Why?

  • Object.hasOwn() is the modern, recommended API (ES2022)
  • hasOwnProperty() can be overridden or shadowed
  • Biome lint rule noPrototypeBuiltins enforces this

Examples

❌ WRONG: Using hasOwnProperty()

if (obj.hasOwnProperty('key')) { /* ... */ }
if (meta.annotations?.codecs?.hasOwnProperty('id')) { /* ... */ }

✅ CORRECT: Using Object.hasOwn()

if (Object.hasOwn(obj, 'key')) { /* ... */ }
if (Object.hasOwn(meta.annotations?.codecs ?? {}, 'id')) { /* ... */ }

Note: When using optional chaining, provide a fallback object:

// ❌ WRONG
Object.hasOwn(meta.annotations?.codecs, 'id')  // May pass undefined

// ✅ CORRECT
Object.hasOwn(meta.annotations?.codecs ?? {}, 'id')
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 · 39 lines · 0 tokens per session scan A 7c05c8e8f830

Subscribe to this mod's changes

object-hasown is a cursor rule published in the GitHub repository prisma/orm (47,579 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 301 tokens. 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-08-30.