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-patch-notesgit 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-patch-notes)<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-patch-notes"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-patch-notes/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-patch-notes"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-patch-notes.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.00046 | $0.00577 |
| Opus 5.5 | $0.00018 | $0.00231 |
| Sonnet 5.5 | $0.00009 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
cgs-patch-notes 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cgs-retrospective — 88% identical, 36 lines differ
What it actually says
Codex Game Studio Patch Notes
Use this skill for patch notes work in Template Game.
Objective
Write player-facing patch notes with fixes, known issues, balance changes, and verification caveats.
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 write player-facing patch notes with fixes, known issues, balance changes, and verification caveats. and identify the current project stage.
- Collect evidence for Player Summary, Fix List, Known Issues.
- 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
- Player Summary
- Fix List
- Known Issues
- Version
- Blocking issues
- Changed files or proposed files
- Verification evidence
- Next owner or decision
Quality Gates
- Player Summary
- Fix List
- Known Issues
- Version
- 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.
- 1mo ago First seen · 80 lines · 46 tokens per session scan A 6f7c20e074b2
cgs-patch-notes is a skill published in the GitHub repository merlinhu1/codex-game-studio (70 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 577 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-30.
Other skills, from other repositories
tools-pipeline-patterns
Design internal tools and content pipelines that reduce manual work and make authoring safer.
godot-editor-tooling
Create Godot editor tools, inspectors, import helpers, and validation flows that reduce manual authoring risk.
unity-editor-tooling
Create Unity editor tools that make content production safer, faster, and less dependent on tribal knowledge.
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
gitlab-ci-patterns
Build GitLab CI/CD pipelines with multi-stage workflows, caching, and distributed runners for scalable automation. Use when implementing GitLab CI/CD, optimizing pipeline performance, or setting up automated testing and deployment.
deployment-pipeline-design
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.