playtest-report

A command for turning playtest findings into decisions, risks, and follow-up actions. A playtest is a session where people try a game so the team can learn what works and what does not.

In plain words
What is it for?
Use it to summarise playtest results, record decisions, identify risks, and assign follow-up work.
Why use it?
It organises scattered observations into conclusions and next steps. This helps teams decide what to change and which risks need attention.

Command for Claude Code

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.

agentmods
npx agentmods add commands/mrcalderon3d/everything-game-dev-code/playtest-report
Clone the repo
git clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-code

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 33 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00033
Opus 5 $0.00008 $0.00016
Sonnet 5 $0.00003 $0.00007
Haiku 4.5 $0.00002 $0.00003

Measured 3d ago against content hash 69741d1739a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 3d 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.

.claude/commands/playtest-report.md · 6 lines

What it actually says

Read commands/playtest-report.md and execute it as instructed.

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. 3d ago First seen · 6 lines · 15 tokens per session scan A 69741d1739a6

Subscribe to this mod's changes

playtest-report is a command published in the GitHub repository MRCalderon3D/everything-game-dev-code (80 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 33 once invoked, about $0.0001 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.