Borrowing it
Nothing to install: this file belongs to SummerEngine/summer-engine-agent. 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/SummerEngine/summer-engine-agent/main/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/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/summerengine/summer-engine-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/summerengine/summer-engine-agent/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.01263 | $0.01263 |
| Opus 5.5 | $0.00505 | $0.00505 |
| Sonnet 5.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 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 — 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.
- 1mo 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 (59 stars, last pushed 1mo ago), licensed MIT. It adds 1,263 tokens to every session, about $0.0051 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-08-30.
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.
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.
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).