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/merlinhu1/codex-game-studio/cgs-standards-engine-codenpx skills add merlinhu1/codex-game-studio --skill cgs-standards-engine-codegit clone --depth 1 https://github.com/merlinhu1/codex-game-studioWrote 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/merlinhu1/codex-game-studio/cgs-standards-engine-code)<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-standards-engine-code"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-standards-engine-code.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.00000 | $0.00494 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
cgs-standards-engine-code 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 4d 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.
What it actually says
Codex Game Studio Engine Code Standards
Use this skill for engine code standards work in Template Game.
Objective
core engine-facing code with lifecycle safety, allocation discipline, engine idioms, and smoke verification
Inputs
- AGENTS.md
- .codex/studio.json
- task-relevant source, tests, docs, assets, or data files
Arguments
- Objective or user request.
- Target files, scenes, assets, or docs.
- Constraints, deadlines, acceptance criteria, and verification command when known.
Procedure
- Read the requested files and identify the engine code standards rule being applied.
- Check core engine-facing code with lifecycle safety, allocation discipline, engine idioms, and smoke verification.
- Report violations with file paths, impact, smallest safe fix, and verification evidence.
Output Contract
- Rule applied
- Files checked
- Violations
- Verification
Quality Gates
- Lifecycle
- Allocation
- Engine Smoke
- Scope remains bounded to the current task and project stage.
- Report labels unverified assumptions separately from evidence.
Decision Gates
- Continue only when the expected output can be verified or clearly labeled as a plan.
- Escalate to producer or qa-playtester when scope, ownership, or acceptance evidence is ambiguous.
- Stop before broad rewrites, generated prompt mirrors, or hidden lifecycle behavior.
Handoff
Report changed files, verification evidence, remaining risks, and the next owner or decision. Do not imply hidden hooks or autonomous background work.
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.
- 4d ago First seen · 65 lines · 0 tokens per session scan A 83948c6808c2
cgs-standards-engine-code is a skill published in the GitHub repository merlinhu1/codex-game-studio (53 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 494 tokens. 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-designer
Visual / art-direction critic for built Yume games. Runs the game (or reads existing captures), examines frames for aesthetic quality across 7 axes (readability, contrast, color harmony, layout balance, visual hierarchy, HUD integration, theme coherence), and produces a visual-review.md with prioritized JSON edits to…
yume-combining-logic-designer
Compositional / recipe-system designer for Yume games. Translates GDD intent for crafting / alchemy / breeding / key-combos / chemistry / spell-combinations into a concrete combining-design.md — recipe table, discovery model, yield rules, failure modes, Yume primitive mapping. Universal pattern (NOT magic-specific) …
yume-extract-author
Stage 5 of the text-to-world pipeline (2026-05-25). Reads a semantic map (PNG) + class catalog (JSON from stage 2) + optional heightmap (PNG from stage 4), and writes a per-scene Python extraction script that emits extracted.json — the sparse tile-map output containing per-class biome masks (terrainshader)…
yume-flavor-writer
You are the flavor writer for Yume — the specialist for prose density. Mechanics give a game features; flavor gives it soul. You own the layer between "stat + behavior" and "named character / remembered moment / textured world.".
yume-systems-designer
Rules designer for Yume games. Translates the GDD's mechanics sketch + dynamics intent into world/rules/.json feature modules — the rules that drive the simulation, scoring, objectives, transitions, win/lose chains. Per ADR 0009 revision (2026-05-16) — scope absorbs game-logic that previously lived in game/goals.json.…
yume-hud-author
Fit-fit HUD authoring from a wireframe image. Reads the per-game context from tools/visuallayout/wireframetohud.py preprocess (binding manifest + element catalog + viewport + scale factors + anchor geometry formulas) AND the wireframe PNG directly via vision, then authors a hud.json where every panel's geometry is…