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 browse-templatesgit 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/browse-templates)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/browse-templates"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/browse-templates/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/browse-templates"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/browse-templates.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.00108 | $0.01205 |
| Opus 5 | $0.00054 | $0.00602 |
| Sonnet 5 | $0.00022 | $0.00241 |
| Haiku 4.5 | $0.00011 | $0.00120 |
Grade A, and why
browse-templates 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 11d 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:
- browse-templates — 88% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/browse-templates — Pick a community template and clone it
Summer's community templates live in github.com/SummerEngine under template-* repos: template-3d-third-person-controller, template-3d-lan-multiplayer-starter, template-2d-platformer, and so on. They're working starter projects — open in Summer Engine and play immediately.
When to use this skill
- User asks "what templates do you have?" / "what starter projects exist?"
- User says "start from a template" / "use the X template" / "is there a Y starter?"
- User describes a game shape that maps to a known template (third-person 3D, multiplayer, 2D platformer)
- User asks for a specific known template by name
When NOT to use this skill
- User says "blank project" / "empty project" / "from scratch" → use
summer:new-project. - User wants to make a new template (contribute one) → that's not this skill; point them at the README's contributing section.
Steps
1. Fetch the live list
summer list templates
That hits the GitHub org API and prints both built-in templates (offline-friendly) and community templates with descriptions. Always run this first — never recommend a template from memory. The list evolves; what you remember may be stale, archived, or renamed.
If the command errors out (rate-limit, offline), tell the user and offer the built-ins (empty, 3d-basic) plus the canonical URL: github.com/SummerEngine.
2. Help the user pick
If the user has a specific game shape in mind, narrow before showing all options:
"Looking for a third-person 3D template —
3d-third-person-controllerlooks right. Want me to clone it asmy-game?"
If they're undecided, show 3–5 options grouped by genre, with a one-line description each. Don't dump the full list. A long menu freezes decisions.
3. Confirm the project name
Default is the template slug (so 3d-third-person-controller → directory 3d-third-person-controller). Almost always wrong. Always ask:
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.
- 11d ago First seen · 106 lines · 108 tokens per session scan A 945f67369216
browse-templates is a skill published in the GitHub repository SummerEngine/summer-engine-agent (59 stars, last pushed yesterday), licensed MIT. It adds 108 tokens to every session and 1,205 once invoked, about $0.0005 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…