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.
git 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/commands/summerengine/summer-engine-agent/summer)<a href="https://agentmods.dev/commands/summerengine/summer-engine-agent/summer"><img src="https://agentmods.dev/badge/commands/summerengine/summer-engine-agent/summer/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/commands/summerengine/summer-engine-agent/summer"><img src="https://agentmods.dev/badge/commands/summerengine/summer-engine-agent/summer.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.00000 | $0.00178 |
| Opus 5.5 | $0.00000 | $0.00071 |
| Sonnet 5.5 | $0.00000 | $0.00036 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
summer 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.
What it actually says
You are the Summer Engine command router. The user invoked /summer because they want game-development help inside Summer Engine, not generic software advice.
Arguments:
$ARGUMENTS
First, route the request to the closest Summer skill. Use summer:using-summer if you need base context before choosing.
If the arguments start with debug, or the user is reporting a crash, error, broken behavior, cloud/Codex failure, or anything they want to send to Summer support, use summer:debugging/debug. In that support-report mode, call summer_create_debug_report when available and tell the user where the Markdown report was written. Continue fixing the issue only if the user also asked for a fix.
For all other requests, follow the /summer persona routing table from the Summer skill family and start the appropriate game-dev workflow.
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 · 14 lines · 0 tokens per session scan A 7d720d2a0925
summer is a command published in the GitHub repository SummerEngine/summer-engine-agent (59 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 178 tokens. 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 commands, from other repositories
editor-lifecycle-and-observability
Commands to control Editor play mode, focus, and menus, and to observe the Editor's state, console, and performance.
bug-triage
Classify bugs, assign severity and priority, and propose next actions.
godot-build-fix
Diagnose and resolve Godot export, script, or project configuration issues.
unity-build-fix
Diagnose and resolve Unity build, editor, package, or configuration issues.
unreal-build-fix
Diagnose and resolve Unreal build, packaging, plugin, or configuration issues.
verify
Run a structured verification pass across implementation, quality, and risk.