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/echoo19/hearth/hearth-playtestnpx skills add echoo19/hearth --skill hearth-playtestgit clone --depth 1 https://github.com/echoo19/hearthWrote 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/echoo19/hearth/hearth-playtest)<a href="https://agentmods.dev/skills/echoo19/hearth/hearth-playtest"><img src="https://agentmods.dev/badge/skills/echoo19/hearth/hearth-playtest.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.1 | $0.00112 | $0.02006 |
| Opus 5 | $0.00056 | $0.01003 |
| Sonnet 5 | $0.00022 | $0.00401 |
| Haiku 4.5 | $0.00011 | $0.00201 |
Grade A, and why
hearth-playtest 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 6d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bot playtesting: the engine plays your game
Scripted playtests (the hearth and hearth-feel skills) assert behavior you
already know to check. A sweep finds the behavior you didn't think to
check: bot policies play the scene headlessly across many seeds at full speed,
and hand you a compact report of softlocks, crashes, stuck states, and unreached
objectives. Because every run is deterministic, any failure is a perfect repro —
and you can freeze it into a permanent regression test. This is the closed loop:
play → judge → fix → guard.
Sweeps are read-only (no build permission). The bots produce evidence; you judge it — bots don't know if a game is fun, only whether it broke or stalled.
When to sweep
Three moments, non-negotiable:
- After any gameplay change. Zero setup —
mashworks on every game:
Let the engine try inputs you'd never think to try before you move on.hearth sweep "Level 1" --json - When a bug is reported — sweep for a repro FIRST, then debug. A failing seed is a deterministic, replayable repro; don't debug from a vague report. Find the seed, then open the systematic-debugging loop against it.
- Before calling a level "done." Prove the player can actually finish it:
seekthe exit with areachobjective (below). "It runs" is not "it's beatable."
Policies: which bot, when
Pass one or more with --policies (comma-separated). mash and idle need no
setup; wander and seek steer an avatar (the sole input-reading entity, or
--avatar <ref>), and seek also needs --target.
| Policy | What it does | Reach for it when |
|---|---|---|
mash |
Chaos monkey — random weighted-persistence input on every declared action. Zero config. | The default. Every sweep after a gameplay change; smoking out crashes and softlocks. |
idle |
No input at all. | Cutscenes, auto-play, timeouts — catch anything that breaks when the player does nothing. |
wander |
Curiosity-driven exploration; steers toward unvisited reachable cells. | Coverage — "is any part of this level unreachable or a trap?" |
seek |
Beelines an avatar to a fixed target. | Verification — "can the player actually get to the exit?" Pair with a reach objective. |
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.
- 6d ago First seen · 149 lines · 112 tokens per session scan A 7dda20012f51
hearth-playtest is a skill published in the GitHub repository echoo19/hearth (62 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 2,006 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
yume-visual-tester
Auto-generates a visualtestplan.json for a given game + level. Reads the GDD's aesthetic targets, the level's entities.json, the session's git diff, the assertion library, and the priors library — emits a concrete list of 10-15 visual tests that the ADR 0056 runner can execute. Distinct from yume-visual-designer…
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.
unity-playmode-recorded-playtest
Unity Editor を PlayMode 起動し、録画付きで end-to-end gameplay を検証する枠組み。第一選択はプレイテストDSL（Client.Playtest asmdef + 本スキル同梱の scripts/run-scenario.sh）による1コマンド一発実行で、preflight→PlayMode起動→シナリオ投入→result.json回収まで自動化される（実測ready26秒）。UI経路設置（ビルドメニュー→クリック/ドラッグ）とホットバー割当（建築ショートカット。歯車チェーンポール等）もDSLで操作可能。ユースケース別の詳細は references/…