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 export-and-shipgit 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/export-and-ship)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/export-and-ship"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/export-and-ship/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/export-and-ship"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/export-and-ship.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.00100 | $0.04538 |
| Opus 5 | $0.00050 | $0.02269 |
| Sonnet 5 | $0.00020 | $0.00908 |
| Haiku 4.5 | $0.00010 | $0.00454 |
Grade A, and why
export-and-ship 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.
How it starts
The opening of the file, as written. The whole thing — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/export-and-ship — Export and Prep Distribution
Overview
Shipping is a checklist, not a creative act. This skill first inventories the export templates and targets actually present in the installed Summer Engine build. It can then validate platform-specific assets and configuration and produce a local build for an available target after approval. It does not upload, host, submit, or promise a target that is absent from the installation.
Core principle: prove the target is locally available, then read its list, satisfy the list, and build. Treat store submission and hosting as separate user-controlled workflows.
Steps
1. Prove local export capability
Do this before presenting destinations, writing presets, or constructing an export command.
- Read
engineBinaryPathfromsummer_get_project_context. - Resolve the matching export-template directory for that exact Summer technical base.
- Inventory the installed templates and any
custom_template/releasepaths already configured inexport_presets.cfg. - Build a capability table with
available,missing prerequisite, orimpossible on this buildfor every requested target.
A stock Summer 4.6.1 Mono install has only the macOS template. Web export is incompatible with that Mono build. Windows, Linux, Android, and iOS require a matching custom template or an external CI/build environment, plus their platform toolchains where applicable.
Hard gate: an absent template or toolchain means the target is unavailable. Do not create its preset, recommend it as a local option, or invoke an export command. Route it to an explicitly configured external CI job or stop and tell the user which prerequisite is missing. An export pack is not a runnable platform build and must not be presented as one.
2. Pick among proven destinations
Offer only targets marked available by step 1. Record other requested
destinations as blocked follow-ups with their exact prerequisite.
Locally proven targets: macOS. Requested but blocked: Windows (matching template or external CI), Web (non-Mono build), Android (template + Android toolchain). Which proven target should I prepare?
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 · 368 lines · 100 tokens per session scan A e86b302d3198
export-and-ship is a skill published in the GitHub repository SummerEngine/summer-engine-agent (59 stars, last pushed yesterday), licensed MIT. It adds 100 tokens to every session and 4,538 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-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…