everything-game-dev-code: Instructions file for Claude Code

CLAUDE.md

everything-game-dev-code CLAUDE.md is an instructions file for Claude Code from MRCalderon3D/everything-game-dev-code. It costs 1,524 tokens per session, scanned A, original, MIT.

Repository instructions for Claude Code, describing a Node.js-based workflow scaffold for AI-assisted game development and its validation commands.

In plain words
What is it for?
They are for maintaining the scaffold, running its tests and validators, and keeping generated files synchronized.
Why use it?
They clarify what the repository contains, which files are authoritative, and how to check for inconsistencies.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

This is MRCalderon3D/everything-game-dev-code's own configuration. It tells Claude Code how to work on everything-game-dev-code itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything everything-game-dev-code configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MRCalderon3D/everything-game-dev-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/MRCalderon3D/everything-game-dev-code/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-code

Made for: Claude Code.

Wrote 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.

agentmods badge for everything-game-dev-code CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mrcalderon3d/everything-game-dev-code/claude-md/github.svg)](https://agentmods.dev/instructions/mrcalderon3d/everything-game-dev-code/claude-md)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for everything-game-dev-code CLAUDE.md

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,524 This file is loaded in full into every session.
When invoked 1,524 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01524 $0.01524
Opus 5.5 $0.00610 $0.00610
Sonnet 5.5 $0.00305 $0.00305
Haiku 4.5 $0.00152 $0.00152

Measured 1mo ago against content hash ea70f01091f8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

CLAUDE.md · 102 lines

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

Read the full file on GitHub · 102 lines

Changes

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.

  1. 1mo ago First seen · 102 lines · 1,524 tokens per session scan A ea70f01091f8

Subscribe to this mod's changes

everything-game-dev-code CLAUDE.md is an instructions file published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 11d ago), licensed MIT. It adds 1,524 tokens to every session, about $0.0061 per session on Opus 5.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.

Related

Other instructions, from other repositories

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens