What is game-build-and-release?

A process for building and checking release files for Phaser or Godot games. Phaser is a web game framework, while Godot is a game engine; a release artifact is the actual package delivered to players.

Use it to define versions and build inputs, create production bundles or exports, inspect files and sizes, run release smoke tests, and verify browser or platform delivery.

It reduces the risk of shipping a build that cannot load, contains secrets, uses wrong paths, or fails on its target platform. It also makes the build reproducible and checks the delivered package itself.

game-build-and-release — Skill for Codex by woliveiras/geremmyas

Install

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.

Any agent

npx skills add woliveiras/geremmyas --skill game-build-and-release

Clone the repo

git clone --depth 1 https://github.com/woliveiras/geremmyas

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/woliveiras/geremmyas/game-build-and-release/github.svg)](https://agentmods.dev/skills/woliveiras/geremmyas/game-build-and-release)

Your own site

<a href="https://agentmods.dev/skills/woliveiras/geremmyas/game-build-and-release"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/game-build-and-release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/woliveiras/geremmyas/game-build-and-release"><img src="https://agentmods.dev/badge/skills/woliveiras/geremmyas/game-build-and-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 472 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00053	$0.00472
Opus 5.5	$0.00021	$0.00189
Sonnet 5.5	$0.00011	$0.00094
Haiku 4.5	$0.00005	$0.00047

Measured 2mo ago against content hash e7ff09cf8339, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

game-build-and-release 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 2mo 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.

content/skills/game-build-and-release/SKILL.md · 47 lines

How it starts

The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Game Build And Release

Produce a versioned artifact from a clean, reproducible process and verify the artifact itself.

Establish the release contract

Read repository instructions and inspect engine, exact version, package manager, export presets, CI, target platforms, hosting, and secret boundaries.
Define artifact names, version source, environment inputs, supported browsers or platforms, and required acceptance.
Separate public build configuration from credentials.
Record required tool and template versions.

Load references

Read release-pipeline.md for reproducibility, artifacts, CI stages, smoke tests, and evidence.
For Phaser, also read phaser.md.
For Godot, also read godot.md.
Use $game-testing-2d for behavior verification and $game-performance-2d for production budgets.

Build and verify

Run source checks and focused tests.
Build from declared inputs with production configuration.
Inspect artifact contents, sizes, hashes, and accidental secrets.
Serve or install the artifact using the real delivery path.
Run a minimal playable smoke route and inspect logs.
Verify cache, base paths, asset loading, save behavior, input, audio, resize, and exit as applicable.
Keep deployment or publication separate unless explicitly authorized.

Report

Provide tool versions, commands, artifact paths and hashes, checks run, failures, warnings, target-specific gaps, and manual acceptance still required.

Guardrails

Do not treat development mode as release verification.
Do not commit credentials or generated secret files.
Do not rename Godot web-export companions independently.
Do not claim tester installation, store approval, or production deployment without direct evidence.
Commit verified local release-engineering changes through the repository's default atomic-commit workflow. Do not publish, upload, tag, push, release, or deploy without explicit authorization.

Read the full file on GitHub · 47 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

2mo ago First seen · 47 lines · 53 tokens per session scan A e7ff09cf8339

Subscribe to this mod's changes

game-build-and-release is a skill published in the GitHub repository woliveiras/geremmyas (10 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 472 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-31.

DevOps and cloud Game development

game-build-and-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
game-build-and-releasewoliveiras/geremmyas	Skill	10	3mo ago	MIT	A	53	Codex
playtest-reportDonchitos/Claude-Code-Game-Studios	Skill	36k	19d ago	MIT	A	20	Claude Code
godot-signals-groupsgamedev-skills/awesome-gamedev-agent-skills	Skill	6.9k	9d ago	Apache-2.0	A	95	Claude Code
scenario-unreal-gameplayscenario-labs/skills	Skill	3.2k	yesterday	MIT	A	121	Claude Code
motionOpenDCAI/GameFactory-3A	Skill	1.0k	8d ago	Apache-2.0	A	0	Claude Code, Codex
unity-addressablesBesty0728/Unity-Skills	Skill	1.9k	yesterday	MIT	A	25	Claude Code, Codex
unity-manual-componentBesty0728/Unity-Skills	Skill	1.9k	yesterday	MIT	A	36	Claude Code, Codex