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 skills/summerengine/summer-engine-agent/make-gamenpx skills add SummerEngine/summer-engine-agent --skill make-gamegit 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/make-game)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/make-game"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/make-game.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.00126 | $0.02665 |
| Opus 5 | $0.00063 | $0.01333 |
| Sonnet 5 | $0.00025 | $0.00533 |
| Haiku 4.5 | $0.00013 | $0.00266 |
Grade A, and why
make-game 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- make-game — 88% identical, 89 lines differ
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/make-game — The orchestration spine
This is the skill that runs end-to-end when a user says "make me a game." It does not try to do everything itself. It runs the right specialist skills in the right order with explicit handoffs and a checkpoint between every phase.
Core principle: structure beats vibes. A guided pipeline that delegates to focused specialists produces a real game. Off-the-cuff "let me think about it" loops produce three half-finished prototypes. Follow the phases. Don't skip.
When to use this skill
- User says: "make me a game", "build me a game", "I want to make a [genre]", "let's build a game", "build me a [shape]".
- User has nothing yet and wants the full path from idea → playable.
- User has a vague idea and wants the agent to drive the whole arc.
When NOT to use this skill
- User has a specific narrow ask ("add jump", "fix this bug", "design the inventory") → use the specific skill, not this orchestrator.
- User already has a working scaffold and wants to iterate → start at the relevant phase below, don't re-run the whole pipeline.
- User says "I want to use a template" → run
summer:browse-templatesfirst; come back here only if they decide they want a custom build instead.
The Pipeline
Brainstorm → Plan → Scaffold → Build → Layer → Polish → Verify → Ship
│ │ │ │ │ │ │ │
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
brainstorm plan new-project build-loop art vfx play export
-game (this browse- (this skill) audio debug -and-
skill) templates ship
↓
(one mechanic at a time:
design-mechanic + scene-composition
+ gdscript-patterns + play check)
Run the phases in order. Between every phase, stop and confirm with the user before continuing. The user owns scope decisions; the agent owns execution discipline.
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.
- 2d ago Changed · +126 tokens per session d0c473c2cb93
- 6d ago First seen · 267 lines · 0 tokens per session scan A 417ce886a65b
make-game is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed yesterday), licensed MIT. It adds 126 tokens to every session and 2,665 once invoked, about $0.0006 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-feel
Make a Hearth game feel good, not just run — the juice stack (hit-stop, screen shake, flash, particle bursts, layered sound), tween easing, camera effects, anticipation/recovery animation idioms, game-UX conventions (menus, pause, onboarding, difficulty, save etiquette), effect-asserting playtests, and the quality bar…