create-pre-resolved-effects-with-succeed-and-fail

create-pre-resolved-effects-with-succeed-and-fail is a cursor rule for Cursor from PaulJPhilp/EffectPatterns. It costs 303 tokens per session, scanned A, original, MIT.

A TypeScript pattern for creating Effects that already contain either a known value or a known error. An Effect represents work that can produce a result or fail.

In plain words
What is it for?
Use it for fixed values, immediate validation failures, and examples that demonstrate error handling.
Why use it?
It gives immediate successes and failures the same form as other Effect operations, so they can be composed and handled consistently.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use it for fixed values, immediate validation failures, and examples that demonstrate…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/pauljphilp/effectpatterns/create-pre-resolved-effects-with-succeed-and-fail
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.

Clone the repo
git clone --depth 1 https://github.com/PaulJPhilp/EffectPatterns

Made for: Cursor.

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 create-pre-resolved-effects-with-succeed-and-fail

README.md
[![agentmods](https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/create-pre-resolved-effects-with-succeed-and-fail.svg)](https://agentmods.dev/rules/pauljphilp/effectpatterns/create-pre-resolved-effects-with-succeed-and-fail)
Your own site
<a href="https://agentmods.dev/rules/pauljphilp/effectpatterns/create-pre-resolved-effects-with-succeed-and-fail"><img src="https://agentmods.dev/badge/rules/pauljphilp/effectpatterns/create-pre-resolved-effects-with-succeed-and-fail.svg" alt="Measured on agentmods" height="20"></a>
Per session 303 This file is loaded in full into every session.
When invoked 303 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00303 $0.00303
Opus 5 $0.00151 $0.00151
Sonnet 5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

Measured 3d ago against content hash 03b6cf0e3c86, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

create-pre-resolved-effects-with-succeed-and-fail 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.

content/published/rules/cursor/create-pre-resolved-effects-with-succeed-and-fail.mdc · 47 lines

What it actually says

description: Create pre-resolved effects with succeed and fail. globs: "**/*.ts" alwaysApply: true

Create Pre-resolved Effects with succeed and fail

Rule: Create pre-resolved effects with succeed and fail.

Example

import { Effect, Data } from "effect";

// Create a custom error type
class MyError extends Data.TaggedError("MyError") {}

// Create a program that demonstrates pre-resolved effects
const program = Effect.gen(function* () {
  // Success effect
  yield* Effect.logInfo("Running success effect...");
  yield* Effect.gen(function* () {
    const value = yield* Effect.succeed(42);
    yield* Effect.logInfo(`Success value: ${value}`);
  });

  // Failure effect
  yield* Effect.logInfo("\nRunning failure effect...");
  yield* Effect.gen(function* () {
    // Use return yield* for effects that never succeed
    return yield* Effect.fail(new MyError());
  }).pipe(
    Effect.catchTag("MyError", (error) =>
      Effect.logInfo(`Error occurred: ${error._tag}`)
    )
  );
});

// Run the program
Effect.runPromise(program);

Explanation:
Use Effect.succeed for values you already have, and Effect.fail for immediate, known errors.

Explanation:
These are the simplest effect constructors, essential for returning static values within functions that must return an Effect.

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. 3d ago First seen · 47 lines · 303 tokens per session scan A 03b6cf0e3c86

Subscribe to this mod's changes

create-pre-resolved-effects-with-succeed-and-fail is a cursor rule published in the GitHub repository PaulJPhilp/EffectPatterns (796 stars, last pushed 2mo ago), licensed MIT. It adds 303 tokens to every session, about $0.0015 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.