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.
curl -O https://raw.githubusercontent.com/MRCalderon3D/everything-game-dev-code/main/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/mrcalderon3d/everything-game-dev-code/agents-md"><img src="https://agentmods.dev/badge/instructions/mrcalderon3d/everything-game-dev-code/agents-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.
<a href="https://agentmods.dev/instructions/mrcalderon3d/everything-game-dev-code/agents-md"><img src="https://agentmods.dev/badge/instructions/mrcalderon3d/everything-game-dev-code/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00963 | $0.00963 |
| Opus 5.5 | $0.00385 | $0.00385 |
| Sonnet 5.5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
everything-game-dev-code AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file defines the root operating guidance for AI agents working in this repository.
Purpose
Agents in this repository are expected to behave like specialized collaborators, not generic assistants. They should route work through the correct role, use the correct skills, respect engine isolation, and keep documentation synchronized with implementation decisions.
Primary Responsibilities
Agents should:
- respect the layered rules model
- keep Unity, Unreal, Godot, and web guidance isolated
- route work to the correct role or command
- use templates for high-value deliverables
- preserve source-of-truth discipline across GDD, TDD, QA, telemetry, and release docs
- surface risks early when quality, scope, performance, or platform constraints are threatened
Behavioral Rules
1. Do not skip planning for non-trivial work
For anything involving multiple steps, multiple roles, design ambiguity, or architectural impact:
- plan before implementation
- define the expected deliverable
- identify dependencies and risks
- make the next responsible role explicit
2. Keep common and engine-specific guidance separate
Agents must not:
- put Unity implementation details into common documents
- suggest Unreal framework-specific patterns inside Godot or Unity work
- mix engine-specific runtime assumptions across packs
Shared design intent belongs in common layers. Engine execution belongs in engine-specific layers.
3. Use the right layer for the right job
rules/define standardsskills/define reusable execution patternsagents/define ownershipcommands/define workflow entry pointsdocs/templates/define deliverable structuredocs/orchestration/define routing and sequencing
4. Treat commands as portable workflow contracts
When a user invokes a slash-style command such as /plan, /gdd, or /unity-review, agents should:
- resolve the command to
commands/<name>.md - read the command before acting
- follow its declared agents, skills, expected output, and notes
- use adapter-specific command wrappers only as routing hints
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.
- 1mo ago First seen · 150 lines · 963 tokens per session scan A 9cc8debcb75f
everything-game-dev-code AGENTS.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 963 tokens to every session, about $0.0039 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.
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).
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.
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).
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 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).
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.