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 new-projectgit 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/new-project)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/new-project"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/new-project/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/skills/summerengine/summer-engine-agent/new-project"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/new-project.svg" alt="Reviewed on agentmods" width="80" 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.00075 | $0.01165 |
| Opus 5 | $0.00037 | $0.00583 |
| Sonnet 5 | $0.00015 | $0.00233 |
| Haiku 4.5 | $0.00007 | $0.00117 |
Grade A, and why
new-project 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 9d 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:
- new-project — 88% identical, 42 lines differ
How it starts
The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-project — Scaffold a fresh empty project
When the user wants to start from a blank canvas — not a community template, not a built-in starter scene — this is the path.
When to use this skill
- "Let's start a new project."
- "I want to make a [game type] from scratch."
- "Blank project."
- "Empty project."
- "I don't want a template, just a blank starting point."
When NOT to use this skill
- "Show me templates" / "use a template" →
summer:browse-templates. - "Make me a game" with a defined idea → run
summer:brainstorm-gamefirst to scope, then come back here once the user knows what they want. - "I have an existing Godot project I want to import" → not this skill; have the user run
summer open <path>directly.
Steps
1. Ask the project name
One question, no menu:
"What do you want to call your project?"
Default: my-game. If they say "anything is fine" or similar, use my-game and move on. The directory name is reversible — they can always rename.
2. Pick the starting scene
Two built-in options:
empty— rootNode3Donly. Pure blank canvas. Best for: experimentation, when the user knows exactly what they want to build.3d-basic— rootNode3DwithCamera3D,DirectionalLight3D, a floorMeshInstance3D, and aWorldEnvironment. Best for: first-time users, when "just give me something I can press play on" is the vibe.
If you're not sure which fits, ask:
"Empty (just a root node) or 3d-basic (camera, light, and a floor — you can press play immediately)?"
If the user has clearly invoked summer:brainstorm-game already and the brief calls for 3D, default to 3d-basic and mention you did. If 2D, use empty (we don't ship a 2D-basic yet).
3. Create
summer create empty my-game
or
summer create 3d-basic my-game
The command writes project.godot and the chosen main.tscn. No network call, fast, deterministic.
4. Open it
summer run my-game
Confirm the engine launched and the project loaded. If summer run fails, run summer doctor and surface the failure to the user.
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.
- 9d ago First seen · 107 lines · 75 tokens per session scan A 96e215d7dacc
new-project is a skill published in the GitHub repository SummerEngine/summer-engine-agent (59 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,165 once invoked, about $0.0004 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…