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/setup-multiplayernpx skills add SummerEngine/summer-engine-agent --skill setup-multiplayergit 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/setup-multiplayer)<a href="https://agentmods.dev/skills/summerengine/summer-engine-agent/setup-multiplayer"><img src="https://agentmods.dev/badge/skills/summerengine/summer-engine-agent/setup-multiplayer.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 | $0.00125 | $0.03670 |
| Opus 5 | $0.00063 | $0.01835 |
| Sonnet 5 | $0.00025 | $0.00734 |
| Haiku 4.5 | $0.00013 | $0.00367 |
Grade A, and why
setup-multiplayer 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 yesterday.
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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup-multiplayer — Add Multiplayer Without Repainting the Project
Overview
Multiplayer is a one-way door. Pick the wrong authority model and refactoring later is brutal. Start with Summer Engine's high-level MultiplayerAPI + MultiplayerSpawner + MultiplayerSynchronizer + ENet. Do not roll custom networking without a measured reason.
Core principle: the architecture decision (peer authority vs server authority) is harder than the code. Lock it before touching a single RPC.
Steps
1. Ask the four blocking questions
Before any code:
- What kind of multiplayer? co-op LAN / co-op online / competitive PvP / lobbies + matchmaking
- How many players? 2 / 2–4 / 8+
- Who runs the simulation? host (one of the players) / dedicated server / authoritative peer-to-peer
- What's the network you're targeting? same Wi-Fi / public internet with ~80ms RTT / mobile
Wait. Each answer flips an irreversible knob.
2. Pick the authority model — irreversible decision
Lock it now. Refactoring authority is a project-killer.
| Model | Best for | Pros | Cons |
|---|---|---|---|
| Host authority (one player runs the sim) | Co-op (2–4 players), casual PvP, friends-only | Cheapest. No server bill. Host migration possible. | Host advantage (no lag for them). Cheating possible. |
| Dedicated server authority | Competitive PvP, matchmaking, > 4 players | Fair. Anti-cheat possible. Stable. | Server bill. Need a deploy story. Higher complexity. |
| Peer-to-peer with shared authority | Lock-step strategy / RTS, fighting games (rollback) | Symmetric latency. No "host advantage". | Determinism is a project on its own. Hard to debug. |
Default recommendation: host authority for co-op (2–4 players), dedicated server for everything else. If user says "competitive PvP" + "lobbies": dedicated.
State the choice explicitly:
Going with host authority for 2–4 player co-op. The first player to start a game is the host. Their scene tree is the source of truth; clients receive replicated state and send input RPCs. Host migration is hard with this model — if the host quits, the game ends. Confirm?
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.
- yesterday Changed · +125 tokens per session 80d1a10ab8cc
- 5d ago First seen · 337 lines · 0 tokens per session scan A 984008009c48
setup-multiplayer is a skill published in the GitHub repository SummerEngine/summer-engine-agent (57 stars, last pushed yesterday), licensed MIT. It adds 125 tokens to every session and 3,670 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…