handle-unexpected-errors-by-inspecting-the-cause

handle-unexpected-errors-by-inspecting-the-cause is a cursor rule for coding agents from PaulJPhilp/EffectPatterns. It costs 340 tokens per session, scanned A, original, MIT.

A TypeScript rule for inspecting Effect's Cause value, which describes why an operation stopped. It distinguishes expected errors, unexpected defects, and interruptions.

In plain words
What is it for?
Use it when logging, analysing, recovering from, or rethrowing failures in Effect programs.
Why use it?
It helps you understand which kind of failure occurred instead of treating every problem as the same error.

Cursor rule

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/pauljphilp/effectpatterns/handle-unexpected-errors-by-inspecting-the-cause
Clone the repo
git clone --depth 1 https://github.com/PaulJPhilp/EffectPatterns

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 handle-unexpected-errors-by-inspecting-the-cause

README.md
[![agentmods](https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/handle-unexpected-errors-by-inspecting-the-cause.svg)](https://agentmods.dev/rules/pauljphilp/effectpatterns/handle-unexpected-errors-by-inspecting-the-cause)
Your own site
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/handle-unexpected-errors-by-inspecting-the-cause"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/handle-unexpected-errors-by-inspecting-the-cause.svg" alt="Measured on agentmods" height="20"></a>
Per session 340 This file is loaded in full into every session.
When invoked 340 The same file — it is already loaded in full.
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.00340 $0.00340
Opus 5 $0.00170 $0.00170
Sonnet 5 $0.00068 $0.00068
Haiku 4.5 $0.00034 $0.00034

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

Security

Grade A, and why

handle-unexpected-errors-by-inspecting-the-cause 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.

content/published/rules/cursor/handle-unexpected-errors-by-inspecting-the-cause.mdc · 46 lines

What it actually says

description: Use Cause to inspect, analyze, and handle all possible failure modes of an Effect, including expected errors, defects, and interruptions. globs: "**/*.ts" alwaysApply: true

Handle Unexpected Errors by Inspecting the Cause

Rule: Use Cause to inspect, analyze, and handle all possible failure modes of an Effect, including expected errors, defects, and interruptions.

Example

import { Cause, Effect } from "effect";

// An Effect that may fail with an error or defect
const program = Effect.try({
  try: () => {
    throw new Error("Unexpected failure!");
  },
  catch: (err) => err,
});

// Catch all causes and inspect them
const handled = program.pipe(
  Effect.catchAllCause((cause) =>
    Effect.sync(() => {
      if (Cause.isDie(cause)) {
        console.error("Defect (die):", Cause.pretty(cause));
      } else if (Cause.isFailure(cause)) {
        console.error("Expected error:", Cause.pretty(cause));
      } else if (Cause.isInterrupted(cause)) {
        console.error("Interrupted:", Cause.pretty(cause));
      }
      // Handle or rethrow as needed
    })
  )
);

Explanation:

  • Cause distinguishes between expected errors (fail), defects (die), and interruptions.
  • Use Cause.pretty for human-readable error traces.
  • Enables advanced error handling and debugging.

Explanation:
Traditional error handling often loses information about why a failure occurred.
Cause preserves the full error context, enabling advanced debugging, error reporting, and robust recovery strategies.

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 · 46 lines · 340 tokens per session scan A 49ca761ec687

Subscribe to this mod's changes

handle-unexpected-errors-by-inspecting-the-cause is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (796 stars, last pushed 2mo ago), licensed MIT. It adds 340 tokens to every session, about $0.0017 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.