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/schema-validationgit 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.00598 |
| Opus 5 | $0.00000 | $0.00299 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
schema-validation 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Effect Schema Validation Patterns
Guidelines for using Effect's Schema system for data validation in the T6C project.
When This Rule Applies
This rule is automatically applied to files that match these patterns:
**/*.types.ts- Type definition files**/schema/**/*.ts- Schema directory files**/schemas/**/*.ts- Schemas directory files**/*-schema.ts- Files ending with-schema.ts**/*-schemas.ts- Files ending with-schemas.ts**/branded.ts- Branded type definition files**/domain/**/*.ts- Domain model files
Import Patterns
Standard Schema Import
- Always use
Schema as Sfor Effect Schema imports - Use relative paths for internal imports
// ✅ CORRECT - Standard import pattern
import { Schema as S } from 'effect'
import { Data, Effect as E } from 'effect'
// ✅ CORRECT - Relative imports for internal types
import { BlogPostId } from '../../domain-common/branded.js'
Branded Types
Basic Branded Types
- Use
S.pipewithS.brandto create type-branded primitives - Export both the schema and the type
export const UserId = S.String.pipe(S.brand('UserId'))
export type UserId = typeof UserId.Type
export const BlogPostId = S.String.pipe(S.brand('BlogPostId'))
export type BlogPostId = typeof BlogPostId.Type
Error Types
Tagged Errors with Data.TaggedError
- Use
Data.TaggedErrorfor domain-specific error types - Include relevant identifiers and context in error data
export class NotFoundError extends Data.TaggedError('NotFoundError')<{
resource: string
id: string
}> {}
export class BlogPostLikeNotFoundError extends Data.TaggedError(
'BlogPostLikeNotFoundError',
)<{
blogPostId: BlogPostId
userId: UserId
}> {}
Schema Testing
Use @effect/vitest for Schema Tests
- Test schema validation with valid and invalid inputs
- Use Effect-based test patterns
import { describe, expect, it } from '@effect/vitest'
import { Effect as E } from 'effect'
describe('BlogPost schema', () => {
it.effect('should decode valid blog post', () =>
E.gen(function* () {
const input = { id: 'blog-1', title: 'Test Post' }
const result = yield* S.decodeUnknown(BlogPost)(input)
expect(result.id).toBe('blog-1')
})
)
})
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 · 90 lines · 598 tokens per session scan A 6c1f42d574df
schema-validation 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 598 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.