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/create-type-safe-errors)<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/create-type-safe-errors"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/create-type-safe-errors.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.00764 | $0.00764 |
| Opus 5 | $0.00382 | $0.00382 |
| Sonnet 5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
create-type-safe-errors 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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Use Data.TaggedError to create typed, distinguishable errors for your domain. globs: "**/*.ts" alwaysApply: true
Create Type-Safe Errors
Rule: Use Data.TaggedError to create typed, distinguishable errors for your domain.
Example
import { Effect, Data } from "effect"
// ============================================
// 1. Define tagged errors for your domain
// ============================================
class UserNotFoundError extends Data.TaggedError("UserNotFoundError")<{
readonly userId: string
}> {}
class InvalidEmailError extends Data.TaggedError("InvalidEmailError")<{
readonly email: string
readonly reason: string
}> {}
class DuplicateUserError extends Data.TaggedError("DuplicateUserError")<{
readonly email: string
}> {}
// ============================================
// 2. Use in Effect functions
// ============================================
interface User {
id: string
email: string
name: string
}
const validateEmail = (email: string): Effect.Effect<string, InvalidEmailError> => {
if (!email.includes("@")) {
return Effect.fail(new InvalidEmailError({
email,
reason: "Missing @ symbol"
}))
}
return Effect.succeed(email)
}
const findUser = (id: string): Effect.Effect<User, UserNotFoundError> => {
// Simulate database lookup
if (id === "123") {
return Effect.succeed({ id, email: "[email protected]", name: "Alice" })
}
return Effect.fail(new UserNotFoundError({ userId: id }))
}
const createUser = (
email: string,
name: string
): Effect.Effect<User, InvalidEmailError | DuplicateUserError> =>
Effect.gen(function* () {
const validEmail = yield* validateEmail(email)
// Simulate duplicate check
if (validEmail === "[email protected]") {
return yield* Effect.fail(new DuplicateUserError({ email: validEmail }))
}
return {
id: crypto.randomUUID(),
email: validEmail,
name,
}
})
// ============================================
// 3. Handle errors by tag
// ============================================
const program = createUser("[email protected]", "Alice").pipe(
Effect.catchTag("InvalidEmailError", (error) =>
Effect.succeed({
id: "fallback",
email: "[email protected]",
name: `${error.email} was invalid: ${error.reason}`,
})
),
Effect.catchTag("DuplicateUserError", (error) =>
Effect.fail(new Error(`Email ${error.email} already registered`))
)
)
// ============================================
// 4. Match on all errors
// ============================================
const handleAllErrors = createUser("bad-email", "Bob").pipe(
Effect.catchTags({
InvalidEmailError: (e) => Effect.succeed(`Invalid: ${e.reason}`),
DuplicateUserError: (e) => Effect.succeed(`Duplicate: ${e.email}`),
})
)
// ============================================
// 5. Run and see results
// ============================================
Effect.runPromise(program)
.then((user) => console.log("Created:", user))
.catch((error) => console.error("Failed:", error))
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.
- 4d ago First seen · 123 lines · 764 tokens per session scan A 52855c4bd6af
create-type-safe-errors is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (796 stars, last pushed 2mo ago), licensed MIT. It adds 764 tokens to every session, about $0.0038 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.