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/flexrpl/cursor-rules-dynamic/cursorrulesgit clone --depth 1 https://github.com/fleXRPL/cursor-rules-dynamicWhat 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.01066 | $0.01066 |
| Opus 5 | $0.00533 | $0.00533 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00107 | $0.00107 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 14 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"version": "1.0.0",
"languages": {
"default": {
"rules": [
{
"id": "rule-1",
"level": "error",
"description": "/ Dynamic .cursorrules Analyzer - VSCode Extension\n// Author: Garot Conklin (garotm)\n\n// What you can build with this ruleset:\nA TypeScript-based VSCode extension that:\n- Automatically analyzes project codebases for patterns and conventions\n- Generates and updates .cursorrules files based on detected patterns\n- Monitors file changes in real-time to suggest rule updates\n- Manages rule versioning and history\n- Integrates directly with VSCode\n- Implements intelligent rule merging and conflict resolution\n- Offers commands for manual rule generation and validation\n\n// Project Structure\nFollow this directory structure:\nsrc/\n extension.ts # Extension activation and setup\n languageDetector.ts # Language detection logic\n test/ # Test files\n runTest/ # Test runner setup\n suite/ # Test suites\n types/ # Type definitions\n\n// Development Guidelines\n1. Code Quality:\n - Use TypeScript 5.x features\n - Enable strict type checking\n - Follow ESLint configuration\n - Maximum line length: 100 characters\n - Use Prettier for formatting\n - Maintain clean code principles\n\n2. Testing Requirements:\n - Maintain 90%+ test coverage\n - Use Mocha test framework\n - Mock VSCode API when needed\n - Test both success and failure cases\n - Include extension activation tests\n - Document test scenarios\n\n3. Documentation Standards:\n - Use TSDoc comments\n - Document all public APIs\n - Include usage examples\n - Maintain up-to-date README\n - Document extension settings\n\n4. Error Handling:\n - Use typed errors\n - Implement proper logging\n - Handle VSCode lifecycle\n - Handle edge cases\n - Provide clear error messages\n\n5. Performance:\n - UsWhat 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.
- 2d ago First seen · 14 lines · 1,066 tokens per session scan A f8d55c25f304
cursorrules is a cursor rule published in the GitHub repository fleXRPL/cursor-rules-dynamic (23 stars, last pushed 1y ago), licensed MIT. It adds 1,066 tokens to every session, about $0.0053 per session on Opus 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-30.
Other cursor rules, from other repositories
engine-internals
Coding Agent engine implementation details (Cursor + Claude Code) — reference when modifying engine.ts or debugging Agent behavior.
testing-conventions
Testing conventions — must reference when modifying src/ code or tests.
architecture-constraints
GolemBot architecture hard constraints — must check before modifying any src/ code.
app_rules
This document outlines the essential rules and guidelines for developing with the MobileLauncher LT boilerplate. Follow these rules to maintain consistency, scalability, and code quality across the project.
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
best_practices
Advanced Best Practices covering Error Handling, Environment Variables, Performance, and Accessibility rules.