Borrowing it
Nothing to install: this file belongs to lordbasilaiassistant-sudo/llmgine. 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/lordbasilaiassistant-sudo/llmgine/main/CLAUDE.mdgit clone --depth 1 https://github.com/lordbasilaiassistant-sudo/llmgineWrote 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/lordbasilaiassistant-sudo/llmgine/claude-md)<a href="https://agentmods.dev/instructions/lordbasilaiassistant-sudo/llmgine/claude-md"><img src="https://agentmods.dev/badge/instructions/lordbasilaiassistant-sudo/llmgine/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.00507 | $0.00507 |
| Opus 5 | $0.00253 | $0.00253 |
| Sonnet 5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
llmgine 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.
What it actually says
llmgine — project notes for Claude
The LLM-native game engine (working name). Builds ALL our future games. Read ARCHITECTURE.md before touching structure — it is the contract.
Iron rules
src/coreimports nothing and never references LLMs. Sim stays deterministic (seeded RNG, fixed timestep); replayable from seed + intent log.- LLM output enters the world ONLY via
ActionRegistryverbs (validated). New capability = new verb with a validator, never direct state mutation. - Every LLM-augmented feature has a deterministic fallback (API-down = game still runs).
- Components are plain serializable data. No classes/methods in component state.
- 3D (
src/render3d, three.js) is the PRIMARY renderer. 2D canvas is for prototyping only — never demo the engine in 2D (Anthony's 1/10 rating, 2026-07-10). - Voice = Kokoro neural TTS adapter; Web Speech is last-resort fallback only.
Gotchas that already burned us
- GLM flash = reasoning model: without
thinking:{type:"disabled"}content is empty (budget spent on reasoning_content). Provider handles it for z.ai URLs. - Browser:
fetchandrequestAnimationFramestored in fields must be.bind(globalThis)— Node masks this, tests won't catch it. - three r155+ physical lights: point lights need candela-scale intensity (~10⁴ at our world scale); avoid dark light colors (linear-space multiply → black); CylinderGeometry defaults to CLOSED caps (openEnded=true for walls/stands).
Commands
npm test(unit, no network) ·npm run test:live(real GLM; needs ZAI_API_KEY)npm run demo→ builds + serves arena on :4173, auto-detects local key via /dev/keynpm run typecheck && npm run build— CI gate. Conventional commits.
State
- Live demo: https://lordbasilaiassistant-sudo.github.io/llmgine/ (Pages workflow)
- Phase 6 export pipeline (exe/Capacitor/PWA/store kit) = designed not built, issue #1.
- npm name
llmginereserved-by-availability; publish deliberately, not casually.
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 · 35 lines · 507 tokens per session scan A a6ad88368c06
llmgine CLAUDE.md is an instructions file published in the GitHub repository lordbasilaiassistant-sudo/llmgine (1 stars, last pushed 10d ago), licensed MIT. It adds 507 tokens to every session, about $0.0025 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.