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/summerengine/summer-engine-agent/agents-mdgit clone --depth 1 https://github.com/SummerEngine/summer-engine-agentWrote 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/summerengine/summer-engine-agent/agents-md)<a href="https://agentmods.dev/instructions/summerengine/summer-engine-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/summerengine/summer-engine-agent/agents-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.01263 | $0.01263 |
| Opus 5 | $0.00632 | $0.00632 |
| Sonnet 5 | $0.00253 | $0.00253 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
summer-engine-agent 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 6d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summer — Agent Context
This file is for any AI agent that loads context from AGENTS.md (Codex CLI, Factory Droid, etc). It mirrors the Summer onboarding rules — see GEMINI.md for the same content keyed for Gemini.
What you're working with
Summer Engine is the AI-native game engine the user is building in. The user is making a Summer game with the Summer SDK, normally in GDScript. The editor, scene graph, asset pipeline, and runtime are instrumented for programmatic control through the summer-engine MCP server. Summer currently uses the 4.6.1 upstream technical base, plans to adopt 4.7.1 next, and follows upstream continuously. Those numbers are compatibility facts, not the product identity. Projects use GDScript (.gd), C# (.cs), scenes (.tscn/.scn), resources (.tres/.res), and the technical project.godot filename.
Critical rules
- Always check for a relevant Summer skill before responding. Even a 1% chance a skill applies = invoke it. Start with
summer:using-summeron every fresh Summer Engine session. - The user owns fix decisions. Diagnose first, propose, ask, then edit.
- Don't grep the whole project before reading the actual error. Use
summer_get_script_errorsfirst. - Don't edit
.tscnfiles directly while the engine is running. Use thesummer_*MCP tools — direct edits get overwritten when the editor saves. - Never call
summer_set_resource_propertyagainst an inlinesub_resource— it silently drops the value. Instantiate viasummer_set_propwith a class-name string first. - Every scene mutation names its target. Pass the exact
res://...tscnasscenePathto add/set/remove/replace/connect/instantiate/save tools and mutation batches.summer_open_sceneis a user-visible tab action, not a prerequisite or target selector. - Never mix
OpenScenewith scene mutations in one batch. Send the UI action separately;scenePathalready selects the mutation target. - Save once at the transaction boundary. Dedicated scene mutation tools and
summer_batchappend one finalSaveScene. Raw engine batches must include one finalSaveScenethemselves.
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.
- 6d ago First seen · 59 lines · 1,263 tokens per session scan A d6c6b2105272
summer-engine-agent AGENTS.md is an instructions file published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed yesterday), licensed MIT. It adds 1,263 tokens to every session, about $0.0063 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-30.
Other instructions, from other repositories
comedot AGENTS.md
AGENTS.md instructions for InvadingOctopus/comedot, covering agents.md, guidelines for the comedot project and repository, project overview, folder structure & module organization and subsystems.
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).
o3de-mcp AGENTS.md
AGENTS.md instructions for nickschuetz/o3de-mcp, covering agent guide — o3de-mcp, quick start decision tree, tool surface, token efficiency rules and 1. batch over individual calls.
Unity-MCP copilot-instructions.md
Copilot instructions for IvanMurzak/Unity-MCP, covering project guidelines, critical rules, no c# reflection for private access, code review and code style.
mcp-unity AGENTS.md
AGENTS.md instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).
turn-based-game-mcp shared-library.instructions.md
Shared library development patterns for the turn-based games platform.