Borrowing it
Nothing to install: this file belongs to sethdford/flowx. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sethdford/flowx/main/.cursorrulesgit clone --depth 1 https://github.com/sethdford/flowxWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/sethdford/flowx/cursorrules)<a href="https://agentmods.dev/rules/sethdford/flowx/cursorrules"><img src="https://agentmods.dev/badge/rules/sethdford/flowx/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/sethdford/flowx/cursorrules"><img src="https://agentmods.dev/badge/rules/sethdford/flowx/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00389 | $0.00389 |
| Opus 5.5 | $0.00156 | $0.00156 |
| Sonnet 5.5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
cursorrules 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 1mo ago.
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.
What it actually says
Claude Flow - Zero Technical Debt Policy
🚨 CRITICAL: NO TECHNICAL DEBT ALLOWED
Core Principles
- ONE IMPLEMENTATION PER FUNCTION - Never create multiple ways to do the same thing
- CONSOLIDATE BEFORE CREATING - Always check for existing implementations before building new ones
- DELETE REDUNDANT CODE - Remove unused, duplicate, or overlapping implementations immediately
- REFACTOR OVER REWRITE - Improve existing code rather than creating parallel implementations
Mandatory Checks Before Any Code Changes
- Does this functionality already exist elsewhere?
- Am I creating a duplicate implementation?
- Can I extend/improve existing code instead?
- Will this create maintenance burden?
- Is this the single source of truth for this functionality?
Forbidden Patterns
❌ Multiple agent spawning implementations ❌ Duplicate database/persistence layers ❌ Overlapping CLI command structures ❌ Similar but slightly different interfaces ❌ Copy-paste code with minor modifications ❌ Multiple ways to achieve the same goal ❌ Temporary implementations that become permanent ❌ "Quick fixes" that bypass existing systems
Required Actions
✅ Consolidate similar implementations into one ✅ Use composition over duplication ✅ Create unified interfaces for common operations ✅ Delete unused/redundant code immediately ✅ Document the single source of truth for each feature ✅ Refactor existing code to be more flexible instead of creating new implementations
Emergency Protocol
If technical debt is identified:
- STOP current development
- Assess scope of duplication
- Create consolidation plan
- Implement unified solution
- Delete redundant implementations
- Update all references
- Test thoroughly
- Document the single source of truth
Remember: Technical debt compounds exponentially. Prevention is 1000x easier than cleanup.
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.
- 1mo ago First seen · 48 lines · 389 tokens per session scan A c4ba7ef3d016
cursorrules is a cursor rule published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 389 tokens to every session, about $0.0016 per session on Opus 5.5. 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
clean-code-reviewer
Eliminates technical debt using SOLID, DRY, YAGNI, and Addy Osmani production-grade engineering principles. / TR: SOLID, DRY, YAGNI ve Addy Osmani üretim seviyesi mühendislik ilkeleri ile kod kalitesini denetleyen yetenek.
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
code-review
BMAD BMM Agent: code-review.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.