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 tettethu/VibeGame --skill vibegame-startgit clone --depth 1 https://github.com/tettethu/VibeGameWrote 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/tettethu/vibegame/vibegame-start)<a href="https://agentmods.dev/skills/tettethu/vibegame/vibegame-start"><img src="https://agentmods.dev/badge/skills/tettethu/vibegame/vibegame-start/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/tettethu/vibegame/vibegame-start"><img src="https://agentmods.dev/badge/skills/tettethu/vibegame/vibegame-start.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.00061 | $0.00577 |
| Opus 5.5 | $0.00024 | $0.00231 |
| Sonnet 5.5 | $0.00012 | $0.00115 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
vibegame-start 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeGame Start
vibegame start already starts the team runtime. Your job is to inspect the existing team state, repair missing persistent members if needed, load project context, and ask the user what to do next.
Startup Checks
- Check team status:
vibegame lead status
- If the team is stopped or no tmux session exists, report that
vibegame startdid not complete and ask the user to restart withvibegame start. Do not create a separate team manually fromvibegame-start. - Check whether persistent members are present:
designerartist
- If
designerorartistis missing, start only the missing member. Use the matching command(s):
vibegame lead agent --agent-type designer --name designer --prompt "You are the persistent designer. Stand by for design work. Do not start work until the lead gives you a task."
vibegame lead agent --agent-type artist --name artist --prompt "You are the persistent artist. Stand by for art work. Do not start work until the lead gives you a task."
Do not wait for designer or artist to reply that they are ready. Their startup can finish asynchronously while you continue.
Shared Startup Steps
After team status is checked:
- Read these files to reinforce your memory and ensure that you know about the current project, the engine, and your workflow:
.vibegame/goal.md.vibegame/GDD.md.vibegame/orchestrator.md.vibegame/spec/engine/index.md(engine quick guide and default runtime rules).vibegame/spec/contracts/index.md(cross-role contract index — you pick the Pattern at task creation time, downstream agents only route).vibegame/spec/test/index.md(regression suite contract)
- Check current task state:
vibegame lead task list
- Report a short startup status to the user:
- Goal
- Whether GDD is filled or needs confirmation
- Task summary
- Ask the user what they want to do next unless they already gave a concrete task.
- After the user gives a task, follow
.vibegame/orchestrator.md.
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.
- 1mo ago First seen · 54 lines · 61 tokens per session scan A 4d10d5f98141
vibegame-start is a skill published in the GitHub repository tettethu/VibeGame (283 stars, last pushed 14d ago), licensed Apache-2.0. It adds 61 tokens to every session and 577 once invoked, about $0.0002 per session on Opus 5.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
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…
hearth-build
Structure a Hearth game's world — scenes, entities, components, tilemaps and autotiling (surfaces must connect), collider/sprite alignment, prefabs, animation state machines, and input bindings. Use when creating or arranging what exists in a Hearth game (levels, objects, hierarchies); behavior scripts are…
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…
hearth
Operate the Hearth engine as a coding agent — the session loop (recall → snapshot → change → validate → playtest → screenshot → remember), project memory, permission modes, verification, review/undo, and export. Load FIRST whenever a project has a hearth.json or the task mentions Hearth. Routes to the domain skills…
hearth-code
Write behavior in Hearth — Lua/JS scripts, the ctx API (input, timers, tweens, events, camera, audio, save), script modules and require, the dot-call and userdata pitfalls, deterministic RNG, and the check-script/edit-script iteration loop. Use when making things happen in a Hearth game (movement, AI, pickups, rules)…
hearth-design
Shape a complete Hearth game, not just working mechanics — scoping to session length (the verbs × levels × enemies budget), the teach → develop → escalate → climax → end arc, real endings (a win state, not just game-over), one-element-at-a-time difficulty ramps, scenes-as-levels pacing with gated progress and…