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-store-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.02619 |
| Opus 5 | $0.00000 | $0.01309 |
| Sonnet 5 | $0.00000 | $0.00524 |
| Haiku 4.5 | $0.00000 | $0.00262 |
Grade A, and why
effect-store-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 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.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect-TS Store 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
../schema/blog-schema.js - Use package imports only for external dependencies
- Store files follow pattern:
store-name.store.ts
// ✅ CORRECT - Relative paths for internal imports
import { BlogSchema } from '../schema/blog-schema.js'
import { ConfigService } from '../../config/config-service.js'
// ✅ CORRECT - Package imports for external dependencies
import { BlogPost, BlogPostId } from '@t6c/blog-domain'
import { Effect as E, Context } from 'effect'
// ❌ WRONG - Never use src/ aliases
import { BlogSchema } from 'src/stores/blog/schema/blog-schema.js'
Store Service Definition
Service Class Structure
export class BlogStore extends E.Service<BlogStore>()('BlogStore', {
dependencies: [DynamoDBDocument.layer({})],
effect: E.gen(function* () {
const dynamodb = yield* DynamoDBService
return {
create: (blogPost: BlogPost) => E.gen(function* () {
// Implementation
}),
getById: (id: BlogPostId) => E.gen(function* () {
// Implementation
}),
}
}),
}) {
static makeTestService = (
mockImplementation: Partial<Omit<BlogStore, '_tag'>>,
) =>
Layer.succeed(BlogStore, {
_tag: 'BlogStore',
create: () => E.die('Not implemented' as const),
getById: () => E.die('Not implemented' as const),
...mockImplementation,
})
}
Configuration Management
Environment Variables in config.ts
- ALWAYS store environment variables in
config.tsusing Effect's Config system - Use
Config.string()for regular values andConfig.redacted()for sensitive data - Provide mock configuration for testing
// config.ts
import { Config, ConfigProvider, Layer } from 'effect'
export const envVars = {
BLOG_TABLE: Config.string('BLOG_TABLE'),
USER_SERVICE_URL: Config.string('USER_SERVICE_URL'),
USER_SERVICE_API_KEY: Config.redacted('USER_SERVICE_API_KEY'),
ALGOLIA_APP_ID: Config.string('ALGOLIA_APP_ID'),
ALGOLIA_SEARCH_API_KEY: Config.redacted('ALGOLIA_SEARCH_API_KEY'),
ALGOLIA_WRITE_API_KEY: Config.redacted('ALGOLIA_WRITE_API_KEY'),
OPENAI_API_KEY: Config.redacted('OPENAI_API_KEY'),
CONTENT_BUCKET: Config.string('CONTENT_BUCKET'),
} as const
const mockConfigProvider = ConfigProvider.fromJson({
BLOG_TABLE: 'blog-table-test',
USER_SERVICE_URL: 'http://localhost:3000',
USER_SERVICE_API_KEY: 'USER_SERVICE_API_KEY',
ALGOLIA_APP_ID: 'ALGOLIA_APP_ID',
ALGOLIA_SEARCH_API_KEY: 'ALGOLIA_SEARCH_API_KEY',
ALGOLIA_WRITE_API_KEY: 'ALGOLIA_WRITE_API_KEY',
OPENAI_API_KEY: 'OPENAI_API_KEY',
CONTENT_BUCKET: 'CONTENT_BUCKET',
})
export const MockConfigLayer = Layer.setConfigProvider(mockConfigProvider)
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 · 376 lines · 2,619 tokens per session scan A a660ff9fcb32
effect-store-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 2,619 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
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.