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 instructions/mrcalderon3d/everything-game-dev-code/claude-mdgit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/claude-md)<a href="https://agentmods.dev/instructions/mrcalderon3d/everything-game-dev-code/claude-md"><img src="https://agentmods.dev/badge/instructions/mrcalderon3d/everything-game-dev-code/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 | $0.01524 | $0.01524 |
| Opus 5 | $0.00762 | $0.00762 |
| Sonnet 5 | $0.00305 | $0.00305 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
everything-game-dev-code 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 yesterday.
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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What this repository is
This is not a game. It is a layered workflow scaffold for AI-assisted game development: a coordinated system of rules, agents, commands, skills, and contexts that a coding assistant loads to do design, technical design, implementation, QA, release, and live-ops work — while keeping the Unity, Unreal, Godot, and web (HTML5) execution layers strictly isolated.
The repository's own "code" is a Node.js (>=18, zero runtime deps) tooling layer under scripts/
that validates and generates the scaffold's content so it can never drift out of sync.
Commands
npm test # node tests/run-all.js — scaffold self-tests
npm run validate # full validation gate (12 validators + markdown lint); this is what CI runs
npm run doctor # diagnose install: env, hooks, active engine profile, artifact drift
npm run setup:hooks # install the git pre-commit hook (first-time setup)
Individual validators (run when iterating on one concern — faster than the full gate):
validate:manifests, validate:engines, validate:hooks, validate:schemas,
validate:structure, validate:references, validate:generated-assets,
validate:structure-artifacts, validate:wrappers, validate:graph, lint:markdown.
Run a single test file directly: node tests/<path>.test.js (e.g. node tests/lib/engine-isolation.test.js).
CI (.github/workflows/ci.yml) runs exactly npm test then npm run validate on Node 18.
The validator list lives only in package.json's validate script so CI and local runs can't diverge.
Source of truth vs. generated artifacts
This is the most important thing to understand before editing. Several files are generated —
editing them by hand is the failure mode CI guards against (a *:check validator re-derives them
and fails if they'd change).
| Edit this (source of truth) | Generates this (do NOT hand-edit) | Sync / check |
|---|---|---|
commands/*.md |
.claude/commands/*, .codex/commands/*, .opencode/* |
npm run sync:wrappers / validate:wrappers |
| tracked file tree | STRUCTURE-TREE.txt, docs/structure-overview.md |
npm run sync:structure / validate:structure-artifacts |
hooks/hooks.json |
harness hook wiring | npm run sync:hook-wiring |
| scaffold layers | docs/dependency-graph.* |
npm run sync:graph / validate:graph |
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.
- yesterday First seen · 102 lines · 1,524 tokens per session scan A ea70f01091f8
everything-game-dev-code CLAUDE.md is an instructions file published in the GitHub repository MRCalderon3D/everything-game-dev-code (80 stars, last pushed 15d ago), licensed MIT. It adds 1,524 tokens to every session, about $0.0076 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-09-03.
Other instructions, from other repositories
yume CLAUDE.md
Instructions for kamwoh/yume, covering yume (夢) — json-driven game framework on godot, quick start, framework structure, how the engine works and tick rate is the engine's heartbeat (2026-05-16).
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).
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.
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.
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).