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 summer-cloudgit 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/summer-cloud)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/summer-cloud"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/summer-cloud.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.00125 | $0.02216 |
| Opus 5 | $0.00063 | $0.01108 |
| Sonnet 5 | $0.00025 | $0.00443 |
| Haiku 4.5 | $0.00013 | $0.00222 |
Grade A, and why
summer-cloud 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summer Cloud: Project Sync
What Summer Cloud is
Summer Cloud is content-addressed sync for a whole Summer Engine project. Every tracked file is identified by its sha256 hash, so identical bytes upload once and dedupe across versions and projects. It syncs the entire project tree at once (code, scenes, resources, import sidecars, and the heavy binary assets), not a hand-picked folder. The only git-tracked cloud artifact is a tiny summer-cloud.json binding at the project root; all real sync state lives under .summer/local/cloud/ and is never committed.
This is not a folder backup and it is not a git replacement. Code that lives happily in git can stay in git. What Cloud adds is a way to move the large generated binaries (models, textures, audio, video) that do not belong in a git repo, and to keep a project byte-identical across machines and collaborators. Git and Cloud can run side by side; the binding file merges trivially.
When to offer it (proactive triggers)
Surface Cloud, do not wait to be asked, when any of these are true:
- The project has heavy generated assets (large
.glb,.png,.wav,.ogg,.mp4underassets/) that should not go into git. Cloud is how those travel. - The user mentions a second machine, a laptop, "my other computer", or working from somewhere else. Cloud is how the same bytes show up there.
- A teammate or collaborator needs the exact same project state. Add them as a collaborator and they pull.
- A risky bulk operation is about to run (mass asset import, a large refactor, a destructive cleanup). A push first gives a restorable version to fall back to.
If none of these apply, do not push Cloud on the user. It is a tool for a real need, not a default step.
Command and tool surface
| Action | CLI | MCP tool |
|---|---|---|
| Enable Cloud for this project | summer cloud init |
summer_cloud_init |
| Show what would push/pull | summer cloud status |
summer_cloud_status |
| Upload local changes | summer cloud push |
summer_cloud_push |
| Download remote changes | summer cloud pull |
summer_cloud_pull |
| Restore an earlier version or a local checkpoint | summer cloud restore --version N / --checkpoint <stamp> |
summer_cloud_restore |
| List local pre-sync checkpoints | summer cloud checkpoints |
summer_cloud_checkpoints |
| List or recover conflict sets | summer cloud conflicts list / restore <path> |
summer_cloud_conflicts |
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 · 93 lines · 125 tokens per session scan A b050a953346d
summer-cloud is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed 3d ago), licensed MIT. It adds 125 tokens to every session and 2,216 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-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…