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 merlinhu1/codex-game-studio --skill cgs-retrospectivegit 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-retrospective)<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-retrospective"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-retrospective/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/merlinhu1/codex-game-studio/cgs-retrospective"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-retrospective.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.00582 |
| Opus 5 | $0.00023 | $0.00291 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
cgs-retrospective 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 11d 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.
This is a copy
88% identical to cgs-patch-notes — 36 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Codex Game Studio Retrospective
Use this skill for retrospective work in Template Game.
Objective
Facilitate a retrospective with what worked, what failed, root causes, actions, and owner follow-up.
Inputs
- AGENTS.md
- .codex/studio.json
- task-relevant files named by the user or task record
- production/timeline.md
- docs/market-overview.md
- tests/
Arguments
- Objective or user request.
- Target files, scenes, assets, or docs.
- Constraints, deadlines, acceptance criteria, and verification command when known.
Procedure
- Clarify the requested facilitate a retrospective with what worked, what failed, root causes, actions, and owner follow-up. and identify the current project stage.
- Collect evidence for Went Well, Did Not Work, Root Cause.
- Separate blockers from warnings and include rollback or deferral options.
- Produce the requested artifact or review with clear file paths and verification evidence.
Write Targets
- production/
- docs/
Output Contract
- Summary
- Went Well
- Did Not Work
- Root Cause
- Action Item
- Blocking issues
- Changed files or proposed files
- Verification evidence
- Next owner or decision
Quality Gates
- Went Well
- Did Not Work
- Root Cause
- Action Item
- 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.
- 11d ago First seen · 80 lines · 45 tokens per session scan A 8bd33e4ab963
cgs-retrospective is a skill published in the GitHub repository merlinhu1/codex-game-studio (54 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 582 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to cgs-patch-notes, differing in 36 lines, and is treated as a copy.
Other skills, from other repositories
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
bug-report
Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
consistency-check
Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
console-get-logs
Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.
editor-application-get-state
Return the current state of UnityEditor.EditorApplication — playmode, paused state, compilation state, and related flags.