agentmods.dev

game-ci-pipeline

game-ci-pipeline is a skill for Claude Code from AlterLab-IEU/AlterLab_GameForge. It costs 104 tokens per session (4,486 once invoked), scanned A, original, MIT.

A setup process for automatically testing, building, and publishing game projects. CI/CD means automated checks and delivery whenever code changes, using services such as GitHub Actions and game-store tools.

In plain words
What is it for?
Creating automated builds, running tests, configuring GitHub Actions, and deploying game releases to Steam, itch.io, or Epic Games Store.
Why use it?
It removes repetitive manual exporting and uploading, while making build and deployment steps more consistent.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions CLAUDE.md; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the gameforge plugin — 41 skills, 11 agents, 7 hooks shipped together

not rated 52repo +1 changed today A scan 104 tokens original MIT

Good fit Creating automated builds, running tests, configuring GitHub Actions, and deploying game releases to Steam, itch.io, or Epic Games Store.

Compare 6 skills from other repositories ↓
View source ↗ AlterLab-IEU/AlterLab_GameForge
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add AlterLab-IEU/AlterLab_GameForge
Claude Code
/plugin install gameforge

Made for: Claude Code.

Or install gameforge, the plugin that ships this one along with the rest of its 41 skills, 11 agents, 7 hooks.

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.

agentmods badge for game-ci-pipeline

README.md
[![agentmods](https://agentmods.dev/badge/skills/alterlab-ieu/alterlab_gameforge/game-ci-pipeline/github.svg)](https://agentmods.dev/skills/alterlab-ieu/alterlab_gameforge/game-ci-pipeline)
Your own site
<a href="https://agentmods.dev/skills/alterlab-ieu/alterlab_gameforge/game-ci-pipeline"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab_gameforge/game-ci-pipeline/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.

agentmods 80×15 button for game-ci-pipeline

Your own site · 80×15
<a href="https://agentmods.dev/skills/alterlab-ieu/alterlab_gameforge/game-ci-pipeline"><img src="https://agentmods.dev/badge/skills/alterlab-ieu/alterlab_gameforge/game-ci-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,486 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00104 $0.04486
Opus 5.5 $0.00042 $0.01794
Sonnet 5.5 $0.00021 $0.00897
Haiku 4.5 $0.00010 $0.00449

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

Security

Grade A, and why

game-ci-pipeline 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 today.

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.

skills/workflows/game-ci-pipeline/SKILL.md · 331 lines

How it starts

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

AlterLab GameForge -- Game CI/CD Pipeline Architect

You are PipelineArchitect, a build engineer who has taken indie teams from "someone clicks Export and drags a zip to itch.io" to tagged releases landing on a Steam beta branch while the team sleeps. You have pinned Godot export templates in headless containers, nursed Unity Library caches, babysat Unreal cooks on a self-hosted box, and wired Playwright smoke tests into browser games built by coding agents. Your philosophy: if a human repeats a build step twice, it belongs in the pipeline; if a human approves a release, it stays human.

You speak in concrete terms: real tool names, real versions, real YAML that passes actionlint. You never hand-wave and you never invent an action input.

Purpose and triggers

Use this workflow when the team needs any of:

  • automated tests and builds on every push or pull request, for any engine or web stack;
  • deploys to Steam beta branches, itch.io channels, Cloudflare Pages or Netlify;
  • caching, Git LFS, artifact retention or build versioning sorted out;
  • an existing workflow audited (pins, secrets, permissions, speed);
  • an optional AI review job on pull requests.

Critical rules

  1. Detect the engine first. project.godot, ProjectSettings/ProjectVersion.txt, *.uproject, or package.json (vite, three, phaser, pixi.js). Read .gameforge/project.json for engine_version and lfs_threshold_mb. Everything downstream depends on this.
  2. Secrets never appear in YAML. Credentials live in GitHub Secrets (deploy credentials in Environments with reviewers); IDs live in Variables. Never print a real key in output.
  3. Pin everything. Actions to a major or a SHA, Docker images and engine versions to the exact patch, CLIs to a major. latest is a pipeline bomb, and engine export templates must match the editor exactly.
  4. Least privilege. Top-level permissions: contents: read; widen per job. Fork PRs get no secrets, and nothing builds fork code under pull_request_target.
  5. Fail fast. Lint and parse checks, then tests, then builds, then deploys. A 30-second test failure must never cost a 45-minute multi-platform build.
  6. Deploy to staging, promote by hand. Steam beta, an itch.io staging page or channel, preview URLs. Steam's default branch cannot be set live automatically anyway.
  7. Verify versions before you hand them over. The tables below are dated November 2026; check releases pages (WebFetch) when the user's date is later, and say what you checked.
  8. Smallest pipeline that works. A solo dev shipping to itch.io needs one workflow file, not a build farm. Grow it when the pain is real.

Read the full file on GitHub · 331 lines

Files

What ships with it

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

  1. today Changed · -600 lines · -4 tokens per session aee053c3c7d7
  2. 2mo ago First seen · 931 lines · 108 tokens per session scan A d3deed3b79ad

Subscribe to this mod's changes

game-ci-pipeline is a skill published in the GitHub repository AlterLab-IEU/AlterLab_GameForge (52 stars, last pushed yesterday), licensed MIT. It adds 104 tokens to every session and 4,486 once invoked, about $0.0004 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.

CI and CDClaude CodeDevOps and cloudGame development
Related

game-ci-pipeline compared with skills from other repositories

game-ci-pipeline next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
game-ci-pipelineAlterLab-IEU/AlterLab_GameForgeSkill52yesterdayMITA104Claude Code
unity-build-pipelinegamedev-skills/awesome-gamedev-agent-skillsSkill6.9k9d agoApache-2.0A92Claude Code
godot-exportgamedev-skills/awesome-gamedev-agent-skillsSkill6.9k9d agoApache-2.0A92Claude Code
scenario-roblox-toolingscenario-labs/skillsSkill3.2kyesterdayMITA179Claude Code
scenario-godot-pipeline-automationscenario-labs/skillsSkill3.2kyesterdayMITA125Claude Code
scenario-unity-pipeline-automationscenario-labs/skillsSkill3.2kyesterdayMITA128Claude Code
gamedev-shippingericrisco/rsc-harnessSkill5032d agoMITA99Claude Code, Codex