What is cgs-playtest-report?

A structured report for recording what players notice and do during a game test. It covers understanding, points of friction, whether players complete the main gameplay loop, bugs, player comments, and design implications.

Use it to document a playtest, record player quotes and problems, check whether the gameplay loop is completed, and connect findings to design decisions.

It turns playtest observations into evidence that a team can use to decide what to fix or change.

cgs-playtest-report — Skill for Claude Code by merlinhu1

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 merlinhu1/codex-game-studio --skill cgs-playtest-report

Clone the repo

git clone --depth 1 https://github.com/merlinhu1/codex-game-studio

Made for: Claude Code.

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/merlinhu1/codex-game-studio/cgs-playtest-report/github.svg)](https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-playtest-report)

Your own site

<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-playtest-report"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-playtest-report/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/merlinhu1/codex-game-studio/cgs-playtest-report"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-playtest-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 582 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.00046	$0.00582
Opus 5	$0.00023	$0.00291
Sonnet 5	$0.00009	$0.00116
Haiku 4.5	$0.00005	$0.00058

Measured 10d ago against content hash 3e59d21cee6f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

cgs-playtest-report 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 10d 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.

.agents/skills/cgs-playtest-report/SKILL.md · 81 lines

What it actually says

Codex Game Studio Playtest Report

Use this skill for playtest report work in Template Game.

Objective

Capture player observations, comprehension, friction, loop completion, bugs, quotes, and design implications.

Inputs

AGENTS.md
.codex/studio.json
task-relevant files named by the user or task record
design/gdd.md
production/session-state/active.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 capture player observations, comprehension, friction, loop completion, bugs, quotes, and design implications. and identify the current project stage.
Collect evidence for Loop Completion, Friction, Observation.
Run or define the focused validation loop before reporting conclusions.
Produce the requested artifact or review with clear file paths and verification evidence.

Write Targets

tests/
production/session-state/
prototypes/

Output Contract

Summary
Loop Completion
Friction
Observation
Design Implication
Risks
Changed files or proposed files
Verification evidence
Next owner or decision

Quality Gates

Loop Completion
Friction
Observation
Design Implication
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.

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.

10d ago First seen · 81 lines · 46 tokens per session scan A 3e59d21cee6f

Subscribe to this mod's changes

cgs-playtest-report is a skill published in the GitHub repository merlinhu1/codex-game-studio (54 stars, last pushed 1mo ago), licensed MIT. It adds 46 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Debugging Game development ai-agents ai-tools codex game-development godot

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.

striderZA/OpenCodeGameStudios · 38 tokens

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.

TraftG/opencode-game-studio · 36 tokens

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.

striderZA/OpenCodeGameStudios · 58 tokens

cgs-playtest-report