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/architecturegit 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.01950 |
| Opus 5 | $0.00000 | $0.00975 |
| Sonnet 5 | $0.00000 | $0.00390 |
| Haiku 4.5 | $0.00000 | $0.00195 |
Grade A, and why
architecture 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeX Cursor Rules - Architectural Enforcement
CRITICAL: Testing Framework Rules
- NEVER use vitest imports - We use Jest exclusively
- ALWAYS import from Jest:
import { describe, test, expect, beforeEach, afterEach, jest } from '@jest/globals' - NEVER import from 'vitest' - This causes build failures
- Test file imports MUST use .ts/.tsx extensions - Never import from .js files that don't exist
- Jest mocks MUST be properly typed - Use
jest.Mock<ReturnType, Args[]>format
Import Path Rules
- Source files: Import from
.ts/.tsxfiles in development - Built files: Only reference
.jsfiles when importing from dist/ - Test files: Always import from TypeScript source files (.ts/.tsx)
- NEVER mix .js and .ts imports in the same file
TypeScript Configuration
- Source code: Must compile with zero TypeScript errors
- Tests: Excluded from main TypeScript compilation to prevent blocking builds
- Build process: Must complete under 50ms for startup performance
Architecture Enforcement
- Performance First: <50ms startup, <40MB runtime, <5MB bundle
- Type Safety: Zero
anytypes, no@ts-ignoresuppressions - Modular Design: Files <300 lines, functions <30 lines
- Error Handling: Custom UserError with category/resolution/details
- No Console Pollution: Use structured logger, never console.log
Testing Standards
- Framework: Jest only (configured in jest.config.js)
- Environment: jsdom for React components
- Coverage: Minimum 10% global, aiming for 90%+
- Mock Strategy: Proper Jest mocks with explicit typing
- Test Structure: Describe/test blocks with clear naming
File Organization
- Source:
src/**/*.tsandsrc/**/*.tsx - Tests:
tests/**/*.test.tsandtests/**/*.test.tsx - Built:
dist/**/*.js(generated, never edit) - Demos: Use tsx to run TypeScript directly
Quality Gates
- Pre-commit:
npm run typecheck && npm run lint && npm run build - TypeScript: Zero errors in src/ directory
- Linting: Address critical errors, defer style issues
- Build: Must succeed and produce working CLI
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 · 198 lines · 0 tokens per session scan A 5452f7acea4f
architecture 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 1,950 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.