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/anashel-rpg/ev2090/cursorrulesgit clone --depth 1 https://github.com/Anashel-RPG/ev2090What 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.01052 | $0.01052 |
| Opus 5 | $0.00526 | $0.00526 |
| Sonnet 5 | $0.00210 | $0.00210 |
| Haiku 4.5 | $0.00105 | $0.00105 |
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EV · 2090 — Cursor Rules
https://ev2090.com | React 19 + Three.js + Cloudflare Workers
The One Rule (Architecture Boundary)
NEVER import React in any file under engine/. NEVER import Three.js in any file under components/.
The engine is pure Three.js. React and the engine communicate only through GameCanvasHandle (imperative ref in GameCanvas.tsx).
The engine pushes GameState to React at ~20fps via a subscribe callback.
When a component needs 3D rendering, create a standalone class in engine/ and instantiate it from the component via useEffect — see ShipPreview.ts and ShipDetailRenderer.ts for the pattern.
Tech Stack
- React 19 + Three.js 0.172 + TypeScript 5.7 + Vite 6 (frontend)
- Cloudflare Workers + Durable Objects + R2 + Queues (backend,
worker/) - MCP server with 37 tools and OAuth 2.0 (
worker-mcp/) - Admin dashboard (
admin/) — local dev only, never deploy - Path alias:
@/→frontend/src/
Key Files
frontend/src/engine/Engine.ts— core game loop, scene, all subsystem orchestrationfrontend/src/components/GameCanvas.tsx— React-to-Engine bridge (forwardRef + useImperativeHandle)frontend/src/components/Game.tsx— top-level React orchestratorfrontend/src/types/game.ts— shared types: GameState, ShipState, RadarContactfrontend/src/engine/ShipCatalog.ts— ship definitions (11 built-in + community)worker/src/index.ts— HTTP router + queue consumerworker/src/economy-region.ts— NPC economy engine (SQLite, 60s tick alarm)worker-mcp/src/index.ts— MCP server entry point
Patterns to Follow
Engine systems (engine/systems/)
Always: constructor(scene, ...) + update(dt) + dispose()
Wire into Engine.ts: instantiate in constructor, call update(dt) in loop, call dispose() in Engine.dispose().
Engine entities (engine/entities/)
Always: constructor(config) + update(dt) + dispose()
Entity owns a THREE.Group as root mesh. scene.add(entity.mesh) in Engine, entity.dispose() on teardown.
All Three.js objects (geometry, materials, textures) MUST be disposed to prevent GPU memory leaks.
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.
- 2d ago First seen · 71 lines · 1,052 tokens per session scan A 95f0f10bc062
cursorrules is a cursor rule published in the GitHub repository Anashel-RPG/ev2090 (10 stars, last pushed 5mo ago), licensed MIT. It adds 1,052 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-31.
Other cursor rules, from other repositories
architecture
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.
unity-performance
Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).
sweep-benchmarks
Audit xrspatial modules for asv benchmark coverage gaps: missing benchmarks, backend parameterization gaps, unrepresentative inputs, broken or silently-skipped benchmarks.
cpp
Cursor rule "cpp" from maddevsio/shared_cursor_rules, covering c++ programming guidelines, basic principles, nomenclature, functions and data.
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.