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.
npx agentmods add rules/charlee-x/effect-cursor-rules/effect-testing-patternsgit clone --depth 1 https://github.com/CharLEE-X/effect-cursor-rulesWhat 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 | $0.00000 | $0.05746 |
| Opus 5 | $0.00000 | $0.02873 |
| Sonnet 5 | $0.00000 | $0.01149 |
| Haiku 4.5 | $0.00000 | $0.00575 |
Grade A, and why
effect-testing-patterns scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
try: () => fetch(url).then(res => res.json()), How it starts
The opening of the file, as written. The whole thing — 836 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect-TS Testing Patterns and Best Practices
Test Framework Setup
Use @effect/vitest for Effect-TS Tests
- Always use
@effect/vitestfor tests involving Effect-based code - Import test functions from
@effect/vitest, not regularvitest - Use
describe,expect, anditfrom@effect/vitest
import { describe, expect, it } from '@effect/vitest'
import { Effect as E, Exit } from 'effect'
Import Patterns - ALWAYS Use Relative Paths
- CRITICAL: Always use relative paths for internal imports, never
src/aliases - Use relative paths like
../../stores/blog/blog.store.js - Use package imports for external dependencies like
@t6c/blog-domain - 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, mockBlogPost1 } from '@t6c/blog-domain'
import { Effect as E } from 'effect'
// ❌ WRONG - Never use src/ aliases in tests
import { BlogStore } from 'src/stores/blog/blog.store.js'
AI Service Testing Patterns
AiStore.generateObject Mocking
- Use
AiStore.makeTestServiceto mock AI operations - Create proper
AiResponse.WithStructuredOutputresponses - Use generic type parameter
<A>()for flexible type handling - Include realistic mock data that matches your schema
import { AiResponse, AiStore } from '@t6c/lib-ai'
// ✅ CORRECT - Complete AI service mocking pattern
const testAiStore = AiStore.makeTestService({
generateObject: <A>() =>
E.succeed(
new AiResponse.WithStructuredOutput({
id: AiResponse.ToolCallId.make('1'),
name: '1',
parts: mockResponse.parts,
value: CommentProcessingOutput.make({
htmlContent: 'test',
status: 'active',
toxicityScore: 0,
sentiment: 'positive',
moderationReason: 'test',
categories: [],
}) as A,
}),
),
})
// ❌ WRONG - Incomplete or incorrect AI mocking
const testAiStore = AiStore.makeTestService({
generateObject: () => E.succeed({ htmlContent: 'test' }), // Missing proper structure
})
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.
- yesterday First seen · 836 lines · 5,746 tokens per session scan A 6bf53625f148
effect-testing-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 5,746 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.