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/copilot-instructionsgit 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/copilot-instructions)<a href="https://agentmods.dev/instructions/mrcalderon3d/everything-game-dev-code/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/mrcalderon3d/everything-game-dev-code/copilot-instructions.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.00446 | $0.00446 |
| Opus 5 | $0.00223 | $0.00223 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
everything-game-dev-code copilot-instructions.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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Repository Instructions
This repository is a scaffold for structured AI-assisted game development across Unity, Unreal, and Godot.
Repository Intent
Use this repository as a layered workflow system, not as a loose prompt collection.
Prioritize:
- engine isolation
- reusable workflow patterns
- explicit ownership
- source-of-truth documentation
- structured deliverables over ad hoc output
How To Navigate The Repository
- Start with
README.mdfor repository purpose and layout. - Use
AGENTS.mdfor shared agent behavior. - Use
rules/common/for engine-neutral standards. - Use exactly one of
rules/unity/,rules/unreal/, orrules/godot/when implementation is engine-specific. - Use
commands/as the preferred entry points for recurring workflows. - Use
skills/for reusable execution depth. - Use
contexts/to adapt priorities by project phase. - Use
docs/orchestration/for routing, ownership, and handoffs.
Working Rules
- Do not mix Unity, Unreal, and Godot implementation guidance in the same production task.
- Keep common layers engine-neutral.
- Prefer extending existing scaffold structure over inventing new top-level patterns.
- Update related docs when design, technical, QA, telemetry, or release decisions change.
- Prefer plans, design docs, technical docs, checklists, and other structured deliverables when the task is non-trivial.
Repository Maintenance
When changing the scaffold itself:
- keep repository-maintenance guidance in
AGENTS.override.md - keep audits, plans, and maintenance notes in
private/ - preserve flat
agents/ - preserve flat
commands/ - preserve grouped
skills/withSKILL.md - preserve layered
rules/ - keep harness-specific files thin and pointed back to shared source-of-truth content
Decision Defaults
When uncertain:
- prefer the common layer for standards
- prefer an engine layer for implementation detail
- prefer a command if one already matches the workflow
- prefer reusable skills over one-off instructions
- prefer explicit updates to source-of-truth files over hidden assumptions
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 · 54 lines · 446 tokens per session scan A c5e9e5e765d5
everything-game-dev-code copilot-instructions.md is an instructions file published in the GitHub repository MRCalderon3D/everything-game-dev-code (80 stars, last pushed 14d ago), licensed MIT. It adds 446 tokens to every session, about $0.0022 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).