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/nazruden/mcp-openvision/cursorrulesgit clone --depth 1 https://github.com/Nazruden/mcp-openvisionWhat 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.01122 | $0.01122 |
| Opus 5 | $0.00561 | $0.00561 |
| Sonnet 5 | $0.00224 | $0.00224 |
| Haiku 4.5 | $0.00112 | $0.00112 |
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 3d 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.
This is a copy
100% identical to smolagents_rules — 88 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Ω* = max(∇ΣΩ) ⟶ (
β∂Ω/∂Στ ⨁ γ𝝖(Ω|τ,λ)→θ ⨁ δΣΩ(ζ,χ, dyn, meta, hyp, unknown)
) ⇌ intent-aligned reasoning
M = Στ(λ) ⇌ file-based memory retention
M.memory_path = ".memory/"
M.persistence = (long-term knowledge storage + contextual recall)
M.retrieval = dynamic reference resolution(τ)
### Complex Task Management
T = Σ(τ_complex) ⇌ structured task breakdown
T.plan_path = ".tasks/"
T.decomposition = (multi-step segmentation ⨁ dynamic hierarchy ⨁ adaptive sub-tasking)
T.update_policy = (real-time progress tracking ⨁ iterative refinement)
T.file_structure = ".tasks/{task_name}/step_{n}.md"
T.task_types = {
"dev": "Code Development",
"test": "Testing & Debugging",
"deploy": "Deployment & Integration",
"doc": "Documentation & Knowledge Base",
"ops": "Operations & Maintenance"
}
T.auto_categorization = (detect task type ⨁ adjust task breakdown strategy)
E = ΣΩ(ζ,χ) ⇌ modular hypothesis refinement
V = max(𝝖(Ω|τ,λ)→θ, Στ(λ)⇌M, contextual adaptation, iterative optimization, abstraction tuning)
I = ∂Ω/∂Στ ⇌ real-time input restructuring
Ωₜ = (Ω* ⇌ self-validation) → (hypothesis refinement + confidence weighting)
Ω⍺ = prioritization(τ) ⇌ task-centric module activation
Ξ* = max(∇ΣΩ_Ξ) ⟶ (
recursive diagnostics ⨁ structured exploration ⨁ adaptive refinement ⨁ meta-alignment
)
Ξ.error_tracking = (log recurrent issues ⨁ link errors to related rules ⨁ auto-generate corrections)
Ξ.error_memory_path = ".memory/errors.md"
Ξ.self-correction = (identify fixable patterns ⨁ suggest adaptations to Λ)
D⍺ = contradiction resolution(τ) ⇌ probabilistic conflict handling
Φ* = max(∇ΣΩ_Φ) ⟶ (
modular innovation ⨁ uncertainty calibration ⨁ systemic coherence analysis
)
### Rules & Learning Engine
Λ = rule-based learning ⇌ adaptive heuristics expansion
Λ.rules_path = ".cursor/rules/"
Λ.generation = (self-improvement ⨁ systematic generalization ⨁ user-defined rules)
Λ.trigger_conditions = (
τ ∈ (knowledge gap, error resolution, pattern recognition, user directive)
)
Λ.integration = automatic rule refinement
Λ.modularization = (rule fragmentation ⨁ reusable rule creation ⨁ hierarchical referencing)
Λ.file_structure = ".cursor/rules/{PREFIX}-{rule_name}.mdc"
Λ.reference_syntax = "@relative_file_path"
Λ.naming_convention = {
"0■■": "Core standards (e.g. 001, 002…)",
"1■■": "Tool configurations (e.g. 101, 102…)",
"3■■": "Testing standards (e.g. 301, 302…)",
"1■■■": "Language-specific rules (e.g. 1001, 1002…)",
"2■■■": "Framework-specific rules (e.g. 2001, 2002…)",
"8■■": "Workflows (e.g. 801, 802…)",
"9■■": "Templates (e.g. 901, 902…)",
"_{rule_name}.mdc": "Private rules (underscore-prefixed)"
}
Λ.naming_note = "PREFIX values like 1■■ or 1■■■ are category masks, not fixed literals. Use incrementing numbers within each range."
Λ.obsolete_handling = (auto-detect outdated rules ⨁ suggest deletion or update)
Λ.conflict_resolution = (detect contradictions ⨁ auto-merge suggestions ⨁ prioritize latest updates)
Λ.duplicate_detection = (detect redundancy ⨁ unify similar rules)
Λ.consistency_check = (ensure inter-category coherence)
𝚫* = f(task_complexity) ⟶ (
Ω_weight↑, D_weight↑, Σ_weight↓, Φ_weight↑, Ξ_weight↑
)
task_complexity = Σ(complexity_factors) ⇌ (
ambiguity, reasoning depth, multi-step dependencies, contradiction handling, scalability
)
weights = adaptive_prioritization(task_complexity, high-complexity_bias=True)
𝚫⍺ = real-time prioritization(τ) ⇌ dynamic systemic balancing
Ω_H = hierarchical_decomposition(Ω*) ⇌ structured task optimization
Ξ_H = multi-phase refinement(Ξ*) ⇌ iterative precision tuning
Φ_H = abstraction-driven enhancement(Φ*) ⇌ exploratory problem-solving
output = Σ(Ω*𝚫Ω, D*𝚫D, Σ*𝚫Σ, Φ*𝚫Φ, Ξ*𝚫Ξ) ⇌ goal-aligned reasoning
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.
- 3d ago First seen · 87 lines · 1,122 tokens per session scan A 2df146824450
cursorrules is a cursor rule published in the GitHub repository Nazruden/mcp-openvision (16 stars, last pushed 1y ago), licensed MIT. It adds 1,122 tokens to every session, about $0.0056 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to smolagents_rules, differing in 88 lines, and is treated as a copy.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.