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 skills add SummerEngine/summer-engine-agent --skill playgit 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/skills/summerengine/summer-engine-agent/play)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/play"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/play.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00053 | $0.00931 |
| Opus 5 | $0.00026 | $0.00465 |
| Sonnet 5 | $0.00011 | $0.00186 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
play 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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/play — Run the Game
Overview
Press play. Watch what happens. Report it back.
Steps
1. Check if it's already running
summer_is_running
If running:
The game is already playing. Stop and restart, or leave it?
Wait for the user. Don't unilaterally stop.
If not running, continue.
2. Pre-check for compile errors
Cheapest call. If the script won't compile, play will fail with a noisy error — better to surface that clearly first.
summer_get_script_errors checks one file and path is required — there is
no project-wide form. Call it on the scripts you just touched:
summer_get_script_errors(path="res://scripts/player.gd")
If you don't know which scripts changed, use summer_get_diagnostics instead —
it takes no arguments and reports editor + runtime counts across the project.
If errors found:
Won't run yet — there's a script error:
<one-line summary>. Want me to /debug it?
Stop here on user's no.
3. Clear and play
summer_clear_console
summer_play
4. Brief wait, then read state
Wait ~2 seconds (so the engine has time to process at least one frame). Then:
summer_get_diagnostics
summer_get_debugger_errors
5. Report
Three outcomes:
Clean: summer_get_diagnostics shows zero errors and zero warnings.
Running. No errors or warnings. Tell me what you see and I'll dig in if needed.
Warnings only:
Running. warnings —
<one-line summary of the most important one>. Want me to look at them?
Runtime error:
Crashed:
<error class>at<file>:<line>—<message>. Want me to /debug?
6. Don't auto-stop
Leave the game running. The user wants to play it. Stop only on explicit ask.
Common patterns
| Situation | Right move |
|---|---|
| User says "play" with no context | Steps 1–5 above |
| User says "play and watch it for me" | After step 5, set a timer / poll summer_get_debugger_errors every few seconds for the duration the user specifies |
| User says "play the boss fight scene" | Pass it directly: summer_play(scene="res://scenes/boss_fight.tscn"). summer_open_scene(path=...) needs a full res:// path too — never a bare relative one |
| Game is already running and user says "play" again | Step 1's check covers it — ask before restarting |
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.
- 8d ago First seen · 115 lines · 53 tokens per session scan A a3ea104dabf8
play is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed 3d ago), licensed MIT. It adds 53 tokens to every session and 931 once invoked, about $0.0003 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 skills, from other repositories
self-evolve
Capture reusable patterns from a finished project and lift them into framework-level priors (contracts, modules, skeletons) that future projects inherit. Run only when the user explicitly requests self-evolution; the orchestrator executes the workflow.
artist-self-evolve
Distill stable art-generation patterns from a completed project, so future projects produce comparable assets without re-discovering the prompts. Lead-dispatched only — orchestrator invokes this skill from its self-evolve flow with a game-slug message; do not self-trigger.
vibegame-build
Run VibeGame's standard end-to-end game development workflow with reviewer gates. Use when the user wants to create a game from zero or evolve an existing game across multiple stages.
vibegame-start
Resume a VibeGame orchestrator session after vibegame start. Use at the beginning of a Claude or Codex session to inspect team runtime state, repair missing persistent members, load goal and GDD context, inspect tasks, and ask the user what to do next.
vibegame-edit
Iterate broadly on an existing game, on top of vibegame-build. Use when the user asks to change an existing game's art style, genre, or core rules. Not for local tuning such as numbers or game feel. Orchestrator only.
hearth-art
Give a Hearth game real art and sound — importing and slicing spritesheets, animations, procedural sprites and sounds, autonomous CC0 asset sourcing (Kenney, itch.io, OpenGameArt, Freesound, Google Fonts) with licensing rules, and pixel-art discipline (never stretch; read the art before using it). Use when the game…