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/PaulJPhilp/EffectPatternsWrote 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/pauljphilp/effectpatterns/handle-missing-values-with-option)<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/handle-missing-values-with-option"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/handle-missing-values-with-option.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.1 | $0.00774 | $0.00774 |
| Opus 5 | $0.00387 | $0.00387 |
| Sonnet 5 | $0.00155 | $0.00155 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
handle-missing-values-with-option 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Use Option instead of null/undefined to make missing values explicit and type-safe. globs: "**/*.ts" alwaysApply: true
Handle Missing Values with Option
Rule: Use Option instead of null/undefined to make missing values explicit and type-safe.
Example
import { Option, Effect } from "effect"
// ============================================
// 1. Creating Options
// ============================================
// Some - a value is present
const hasValue = Option.some(42)
// None - no value
const noValue = Option.none<number>()
// From nullable - null/undefined becomes None
const fromNull = Option.fromNullable(null) // None
const fromValue = Option.fromNullable("hello") // Some("hello")
// ============================================
// 2. Checking and extracting values
// ============================================
const maybeUser = Option.some({ name: "Alice", age: 30 })
// Check if value exists
if (Option.isSome(maybeUser)) {
console.log(`User: ${maybeUser.value.name}`)
}
// Get with default
const name = Option.getOrElse(
Option.map(maybeUser, u => u.name),
() => "Anonymous"
)
// ============================================
// 3. Transforming Options
// ============================================
const maybeNumber = Option.some(5)
// Map - transform the value if present
const doubled = Option.map(maybeNumber, n => n * 2) // Some(10)
// FlatMap - chain operations that return Option
const safeDivide = (a: number, b: number): Option.Option<number> =>
b === 0 ? Option.none() : Option.some(a / b)
const result = Option.flatMap(maybeNumber, n => safeDivide(10, n)) // Some(2)
// ============================================
// 4. Domain modeling example
// ============================================
interface User {
readonly id: string
readonly name: string
readonly email: Option.Option<string> // Email is optional
readonly phone: Option.Option<string> // Phone is optional
}
const createUser = (name: string): User => ({
id: crypto.randomUUID(),
name,
email: Option.none(),
phone: Option.none(),
})
const addEmail = (user: User, email: string): User => ({
...user,
email: Option.some(email),
})
const getContactInfo = (user: User): string => {
const email = Option.getOrElse(user.email, () => "no email")
const phone = Option.getOrElse(user.phone, () => "no phone")
return `${user.name}: ${email}, ${phone}`
}
// ============================================
// 5. Use in Effects
// ============================================
const findUser = (id: string): Effect.Effect<Option.Option<User>> =>
Effect.succeed(
id === "123"
? Option.some({ id, name: "Alice", email: Option.none(), phone: Option.none() })
: Option.none()
)
const program = Effect.gen(function* () {
const maybeUser = yield* findUser("123")
if (Option.isSome(maybeUser)) {
yield* Effect.log(`Found: ${maybeUser.value.name}`)
} else {
yield* Effect.log("User not found")
}
})
Effect.runPromise(program)
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.
- 3d ago First seen · 121 lines · 774 tokens per session scan A 0e848b631128
handle-missing-values-with-option is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (796 stars, last pushed 2mo ago), licensed MIT. It adds 774 tokens to every session, about $0.0039 per session on Opus 5. 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-09-03.
Other cursor rules, from other repositories
typescript-code-generation-rules
Rules for generating TypeScript code in Next.js 14 components, including component definition syntax, props definitions, and named/default exports.
lspsteer
Compiler-in-the-loop type checking for code edits via LSPSteer.
react-and-typescript-general-rules
General rules for React and TypeScript projects, focusing on code clarity and best practices.
javascript-typescript-code-style
Rules for JavaScript and TypeScript code style, including modern features, functional patterns, and descriptive naming conventions.
javascript-expert-performance
Profile first. Measure before and after. Never optimize without data.
typescript-usage-rules
Specific rules for TypeScript usage, including interfaces, union types, and type guards to enhance type safety.