Borrowing it
Nothing to install: this file belongs to Anashel-RPG/ev2090. 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/Anashel-RPG/ev2090/main/CLAUDE.mdgit clone --depth 1 https://github.com/Anashel-RPG/ev2090Wrote 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/instructions/anashel-rpg/ev2090/claude-md)<a href="https://agentmods.dev/instructions/anashel-rpg/ev2090/claude-md"><img src="https://agentmods.dev/badge/instructions/anashel-rpg/ev2090/claude-md.svg" alt="Measured on agentmods" 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.03724 | $0.03724 |
| Opus 5 | $0.01862 | $0.01862 |
| Sonnet 5 | $0.00745 | $0.00745 |
| Haiku 4.5 | $0.00372 | $0.00372 |
Grade A, and why
ev2090 CLAUDE.md 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 7d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — Project Context for AI Assistants
Project
EV · 2090 — a 3D space simulation game with a live NPC economy. Live: https://ev2090.com | API: https://ws.ev2090.com | MCP: https://mcp.ev2090.com
Tech Stack
- Frontend: React 19 + Three.js 0.172 + TypeScript 5.7 + Vite 6
- Backend: Cloudflare Workers + Durable Objects + R2 + Queues
- MCP Server: 37 tools, OAuth 2.0 PKCE (
worker-mcp/) - Admin Dashboard: React + Vite, local-only, never deployed (
admin/) - Monorepo: 4 npm workspaces —
frontend/,worker/,worker-mcp/,admin/
Architecture — The One Rule
The engine (frontend/src/engine/) is pure Three.js with ZERO React dependencies.
React communicates with the engine only through GameCanvasHandle (imperative ref in GameCanvas.tsx).
The engine pushes GameState to React at ~20fps via a subscribe callback.
NEVER import React in engine/ files. NEVER import Three.js in components/ files.
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.
Key Files
| File | Purpose |
|---|---|
frontend/src/engine/Engine.ts |
Core game loop, scene, renderer, all subsystem orchestration |
frontend/src/components/GameCanvas.tsx |
React-to-Engine bridge (forwardRef + useImperativeHandle) |
frontend/src/components/Game.tsx |
Top-level React orchestrator — state, layout, breakpoints |
frontend/src/types/game.ts |
Shared types: GameState, ShipState, RadarContact, LightConfig |
frontend/src/engine/ShipCatalog.ts |
Ship definitions (11 built-in + community registry) |
worker/src/index.ts |
HTTP router + CORS + queue consumer |
worker/src/chat-room.ts |
Durable Object — SSE chat, 7 messages, ping keep-alive |
worker/src/board-room.ts |
Durable Object — community notes per planet station |
worker/src/ship-forge.ts |
Durable Object — AI ship pipeline (Grok → Gemini → MeshyAI) |
worker/src/economy-region.ts |
Durable Object — NPC economy simulation (SQLite, 60s alarm tick) |
worker/src/admin.ts |
Admin API endpoints (auth required via ADMIN_API_KEY) |
worker-mcp/src/index.ts |
MCP server entry point — 37 tools, OAuth 2.0 PKCE |
admin/src/App.tsx |
Admin dashboard SPA — Economy, Region Detail, Infra Health, Trade Viewer |
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.
- 7d ago First seen · 291 lines · 3,724 tokens per session scan A 8c01c9d4f4b6
ev2090 CLAUDE.md is an instructions file published in the GitHub repository Anashel-RPG/ev2090 (10 stars, last pushed 6mo ago), licensed MIT. It adds 3,724 tokens to every session, about $0.0186 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.