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/sethdford/flowx/typescript-rulesgit clone --depth 1 https://github.com/sethdford/flowxWhat 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.02931 |
| Opus 5 | $0.00000 | $0.01465 |
| Sonnet 5 | $0.00000 | $0.00586 |
| Haiku 4.5 | $0.00000 | $0.00293 |
Grade A, and why
typescript-rules 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 — 473 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TypeScript Rules: Zero Tolerance for Type Errors + Community Wisdom
🚨 CRITICAL TYPE SAFETY RULES
NEVER Use These (Auto-Reject)
// ❌ FORBIDDEN - Will break our type safety
any
@ts-ignore // without detailed explanation
@ts-expect-error // without test case
as any
<any>
Function // Use proper function signatures
Object // Use proper object types
{} // Use proper interface/type
ALWAYS Use These Patterns
// ✅ REQUIRED - Proper type definitions
interface UserData {
readonly id: string;
readonly name: string;
readonly email: string;
readonly createdAt: Date;
}
// ✅ REQUIRED - Proper error types
type ApiError = {
readonly code: string;
readonly message: string;
readonly details?: Record<string, unknown>;
};
// ✅ REQUIRED - Proper function signatures
type ProcessUser = (user: UserData) => Promise<ProcessResult>;
type ValidateInput = <T>(input: unknown, schema: Schema<T>) => T;
📝 COMMUNITY-PROVEN PATTERNS
1. Functional Programming with Types
// ✅ REQUIRED - Functional and declarative patterns
// From cursor.directory research: "Use functional and declarative programming patterns; avoid classes"
// ❌ FORBIDDEN - Classes
class UserProcessor {
process(user: User): Result { /* ... */ }
}
// ✅ REQUIRED - Functional approach with proper types
type UserProcessor = (user: User) => Result;
type ProcessResult<T> = {
readonly success: boolean;
readonly data?: T;
readonly error?: string;
};
const processUser: UserProcessor = (user) => {
// Process functionally
return { success: true, data: transformedUser };
};
2. Interface over Types (Community Standard)
// ✅ REQUIRED - Use interfaces for object shapes
// From research: "Use TypeScript for all code; prefer interfaces over types"
interface ComponentProps {
readonly title: string;
readonly onComplete: (result: CompletionResult) => void;
readonly isLoading?: boolean;
}
interface ApiResponse<T> {
readonly data: T;
readonly status: number;
readonly message: string;
}
// ✅ REQUIRED - Types for unions and computations
type Status = 'idle' | 'loading' | 'success' | 'error';
type EventHandler<T> = (event: T) => void;
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 · 473 lines · 0 tokens per session scan A 4e9d98d22748
typescript-rules is a cursor rule published in the GitHub repository sethdford/flowx (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,931 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.