Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rulesnpx agentmods add rules/charlee-x/effect-cursor-rules/effect-usecase-patternsWrote 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/charlee-x/effect-cursor-rules/effect-usecase-patterns)<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/effect-usecase-patterns"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/effect-usecase-patterns/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/charlee-x/effect-cursor-rules/effect-usecase-patterns"><img src="https://agentmods.dev/badge/rules/charlee-x/effect-cursor-rules/effect-usecase-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.06271 |
| Opus 5.5 | $0.00000 | $0.02508 |
| Sonnet 5.5 | $0.00000 | $0.01254 |
| Haiku 4.5 | $0.00000 | $0.00627 |
Grade A, and why
effect-usecase-patterns 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 1mo 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 — 792 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect-TS Usecase Implementation Patterns and Best Practices
Import Patterns
Always Use Relative Paths for Internal Imports
- CRITICAL: Never use
src/aliases for internal imports - Always use relative paths like
../../stores/blog/blog.store.js - Use package imports only for external dependencies
- Store files follow pattern:
store-name.store.ts
// ✅ CORRECT - Relative paths for internal imports
import { BlogStore } from '../../stores/blog/blog.store.js'
import { SearchStore } from '../../stores/search/search.store.js'
// ✅ CORRECT - Package imports for external dependencies
import { BlogPost, BlogPostId } from '@t6c/blog-domain'
import { Effect as E } from 'effect'
// ❌ WRONG - Never use src/ aliases
import { BlogStore } from 'src/stores/blog/blog.store.js'
MANDATORY Usecase Structure
Required Error Handling and Observability Pattern
EVERY usecase MUST follow this exact pattern:
export const myUsecase = (input: MyInput) =>
E.gen(function* () {
// Business logic implementation here...
const result = yield* businessLogic(input)
return result
}).pipe(
// 🔴 MANDATORY: Simple error logging - NO custom messages
E.tapError(E.logError),
// 🔴 MANDATORY: Use E.orDie for unexpected errors OR allow domain errors to bubble up
E.orDie, // Use this for usecases that should only return success
// 🔴 MANDATORY: Observability span with relevant attributes
E.withSpan('my-usecase-name', {
attributes: {
// Only include primitive values, not entire objects
userId: input.userId,
page: input.page
}
}),
)
Error Handling Strategy by Usecase Type
GET Usecases - Allow NotFoundError to Bubble Up
// ✅ CORRECT - Allow NotFoundError for client handling
export const getBlogByIdUsecase = (id: BlogPostId) =>
E.gen(function* () {
const blogStore = yield* BlogStore
const userStore = yield* UserStore
const blogPost = yield* blogStore.getById(id) // Can throw NotFoundError
const author = yield* userStore.getAuthorById(blogPost.authorId)
return BlogPostProfile.make({
// ... transformation
})
}).pipe(
E.tapError(E.logError), // ✅ Simple logging only
// ❌ NO E.orDie - let NotFoundError bubble up
E.withSpan('getBlogByIdUsecase', {
attributes: { blogPostId: id }
})
)
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.
- 1mo ago First seen · 792 lines · 6,271 tokens per session scan A e72e9b4f664a
effect-usecase-patterns is a cursor rule published in the GitHub repository CharLEE-X/effect-cursor-rules (6 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 6,271 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-31.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.
selectools-providers
Rules for working with LLM provider adapters in selectools.