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 hoatv2211/GameStudio-CodexKIT --skill playtest-evidencegit clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKITWrote 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/hoatv2211/gamestudio-codexkit/playtest-evidence)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/playtest-evidence"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/playtest-evidence.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.1 | $0.00037 | $0.00752 |
| Opus 5 | $0.00018 | $0.00376 |
| Sonnet 5 | $0.00007 | $0.00150 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
playtest-evidence 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playtest Evidence
Overview
Convert playtest notes into traceable evidence without turning opinions, memories, or small samples into invented metrics.
When to use
Use for usability sessions, mechanic validation, onboarding tests, combat feel reviews, retention hypotheses, and regression playtests.
When NOT to use
Do not use as a substitute for automated correctness tests, production analytics, or statistically representative research.
Required inputs and context discovery
Collect build identity, feature hypothesis, participant context, scenario, environment, session method, consent constraints, observation timestamps, issue reproduction, and protected personal data rules.
Safety and risk level
Read-only evidence synthesis. Remove personal data, do not record participants without consent, and label missing builds, recordings, or reproduction artifacts as BLOCKED or Unverified.
Workflow
- Bind the session to an exact build, feature hypothesis, and scenario. Completion criterion: the tested state and intended question are explicit.
- Separate direct observation, participant quote, facilitator interpretation, and proposed fix. Completion criterion: every finding has one evidence class and source reference.
- Normalize issues by reproduction, severity, frequency within the observed sample, and affected experience. Completion criterion: no issue uses unsupported population-level claims.
- Compare results with the playtest criteria from the feature specification. Completion criterion: each criterion is Verified, Unverified, FAIL, or BLOCKED with a reason.
- Produce follow-up experiments and regression checks. Completion criterion: each next step has an owner, artifact, and stopping condition.
Evidence and output contract
Produce playtest-evidence.json with build identity, scenarios, participant context, observations, issues, criteria verdicts, limitations, and follow-up experiments.
Handoff contract
Record session artifacts, privacy redactions, reproduced issues, unresolved disagreements, test gaps, next owners, and the build required for follow-up.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 79 lines · 37 tokens per session scan A 869a2bc8fd4a
playtest-evidence is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 752 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-31.
Other skills, from other repositories
vibe-adversarial-test-generation
Generates edge case, failure mode, and spec-driven test cases. Covers boundary values, nil inputs, concurrency, resource exhaustion, malformed data, and requirement-linked traceability tests.
vibe-coverage-enforcer
Enforces tiered test coverage standards with three dimensions — line coverage by tier, spec-to-test traceability, and spec-to-code implementation mapping. Use before claiming code is complete.
vibe-fuzz-parser-inputs
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input). Seeds corpus from existing fixtures and runs initial pass.
vibe-concurrent-test-safety
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering. Use when writing tests that involve goroutines, async operations, or shared mutable state.
vibe-golden-file-testing
Implements snapshot/golden file tests with temporal normalization so tests don't break daily. Use when implementing tests that compare output against expected snapshots.
vibe-quality-loop
Enforces the Implement→Review→Test→Fix→Loop cycle until work is clean. Use after any non-trivial implementation to prevent "good enough" exits.