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 agentmods add skills/pixel-cellar/claude-code-game-studios/gate-checknpx skills add pixel-cellar/Claude-Code-Game-Studios --skill gate-checkgit clone --depth 1 https://github.com/pixel-cellar/Claude-Code-Game-StudiosWrote 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/pixel-cellar/claude-code-game-studios/gate-check)<a href="https://agentmods.dev/skills/pixel-cellar/claude-code-game-studios/gate-check"><img src="https://agentmods.dev/badge/skills/pixel-cellar/claude-code-game-studios/gate-check.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 | $0.00000 | $0.02663 |
| Opus 5 | $0.00000 | $0.01332 |
| Sonnet 5 | $0.00000 | $0.00533 |
| Haiku 4.5 | $0.00000 | $0.00266 |
Grade A, and why
gate-check 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 4d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
可以将翻译结果写入 .claude/skills/gate-check/SKILL.md 吗？
---
name: gate-check
description: "验证项目是否准备好进入下一个开发阶段。产出 PASS/CONCERNS/FAIL 判定结果，附带具体的阻碍项和所需工件。"
argument-hint: "[目标阶段: systems-design | technical-setup | pre-production | production | polish | release]"
user-invocable: true
allowed-tools: Read, Glob, Grep, Bash, Write
---
# 阶段关卡验证
此技能验证项目是否已准备好进入下一个开发阶段。
它会检查所需工件、质量标准和阻碍项。
**与 `/project-stage-detect` 的区别**：该技能是诊断性的（"我们在哪？"）。
本技能是规范性的（"我们准备好推进了吗？"并附带正式判定）。
## 生产阶段（7 个）
项目依次经历以下阶段：
1. **概念** — 头脑风暴、游戏概念文档
2. **系统设计** — 映射系统、编写 GDD（游戏设计文档）
3. **技术搭建** — 引擎配置、架构决策
4. **前期制作** — 原型开发、垂直切片验证
5. **正式制作** — 功能开发（Epic/Feature/Task 跟踪已激活）
6. **打磨** — 性能优化、试玩测试、缺陷修复
7. **发布** — 上线准备、平台认证
**当关卡通过时**，将新阶段名称写入 `production/stage.txt`
（单行，例如 `Production`）。这会立即更新状态栏。
---
## 1. 解析参数
- **带参数**：`/gate-check production` — 验证是否准备好进入指定阶段
- **无参数**：使用与 `/project-stage-detect` 相同的启发式方法自动检测当前阶段，
然后验证下一个阶段转换
---
## 2. 阶段关卡定义
### 关卡：概念 → 系统设计
**所需工件：**
- [ ] `design/gdd/game-concept.md` 存在且有内容
- [ ] 游戏支柱已定义（在概念文档或 `design/gdd/game-pillars.md` 中）
**质量检查：**
- [ ] 游戏概念已经过评审（`/design-review` 判定结果非"需要重大修订"）
- [ ] 核心循环已描述且已理解
- [ ] 目标受众已确定
---
### 关卡：系统设计 → 技术搭建
**所需工件：**
- [ ] 系统索引存在于 `design/gdd/systems-index.md`，至少枚举了 MVP 系统列表
- [ ] `design/gdd/` 中至少有 1 份 GDD（game-concept.md 和 systems-index.md 之外的）
**质量检查：**
- [ ] GDD 通过设计评审（8 个必需章节齐全）
- [ ] 系统依赖关系已在系统索引中映射
- [ ] MVP 优先级层级已定义
---
### 关卡：技术搭建 → 前期制作
**所需工件：**
- [ ] 引擎已选定（CLAUDE.md 中的技术栈不再是 `[CHOOSE]`）
- [ ] 技术偏好已配置（`.claude/docs/technical-preferences.md` 已填写）
- [ ] `docs/architecture/` 中至少有 1 份架构决策记录（ADR）
- [ ] 引擎参考文档存在于 `docs/engine-reference/`
**质量检查：**
- [ ] 架构决策覆盖核心系统（渲染、输入、状态管理）
- [ ] 技术偏好已设置命名规范和性能预算
---
### 关卡：前期制作 → 正式制作
**所需工件：**
- [ ] `prototypes/` 中至少有 1 个带 README 的原型
- [ ] `production/sprints/` 中存在首个 Sprint 计划
- [ ] 系统索引中所有 MVP 层级的 GDD 均已完成
**质量检查：**
- [ ] 原型验证了核心循环假设
- [ ] Sprint 计划引用了 GDD 中的真实工作项
- [ ] 垂直切片范围已定义
---
### 关卡：正式制作 → 打磨
**所需工件：**
- [ ] `src/` 中有按子系统组织的有效代码
- [ ] GDD 中的所有核心机制已实现（交叉比对 `design/gdd/` 与 `src/`）
- [ ] 主要游玩路径可从头玩到尾
- [ ] 测试文件存在于 `tests/`
- [ ] 至少有 1 份试玩报告（或已运行 `/playtest-report`）
**质量检查：**
- [ ] 测试通过（通过 Bash 运行测试套件）
- [ ] 任何 Bug 跟踪器或已知问题中没有严重/阻断级 Bug
- [ ] 核心循环游玩效果符合设计（对照 GDD 验收标准）
- [ ] 性能在预算范围内（检查 technical-preferences.md 中的目标）
---
### 关卡：打磨 → 发布
**所需工件：**
- [ ] 里程碑计划中的所有功能已实现
- [ ] 内容已完成（设计文档中引用的所有关卡、资源、对话均已存在）
- [ ] 本地化字符串已外部化（`src/` 中无硬编码的面向玩家的文本）
- [ ] QA 测试计划已存在
- [ ] 平衡数据已经过评审（已运行 `/balance-check`）
- [ ] 发布清单已完成（已运行 `/release-checklist` 或 `/launch-checklist`）
- [ ] 商店元数据已准备（如适用）
- [ ] 更新日志/补丁说明已起草
**质量检查：**
- [ ] 完整的 QA 轮次已由 `qa-lead` 签字确认
- [ ] 所有测试通过
- [ ] 性能目标在所有目标平台上均已达成
- [ ] 无已知的严重、高或中等级别 Bug
- [ ] 无障碍基础项已覆盖（按键重映射、文本缩放等，如适用）
- [ ] 所有目标语言的本地化已验证
- [ ] 法律要求已满足（EULA、隐私政策、年龄评级等，如适用）
- [ ] 构建编译和打包正常
---
## 3. 执行关卡检查
针对目标关卡中的每一项：
### 工件检查
- 使用 `Glob` 和 `Read` 验证文件存在且有实质性内容
- 不要只检查文件是否存在 — 验证文件有真实内容（不仅仅是模板头部）
- 对于代码检查，验证目录结构和文件数量
### 质量检查
- 对于测试检查：如果配置了测试运行器，通过 `Bash` 运行测试套件
- 对于设计评审检查：`Read` GDD 并检查 8 个必需章节
- 对于性能检查：`Read` technical-preferences.md 并与 `tests/performance/` 中的
性能分析数据或最近的 `/perf-profile` 输出进行对比
- 对于本地化检查：在 `src/` 中使用 `Grep` 搜索硬编码字符串
### 交叉引用检查
- 将 `design/gdd/` 文档与 `src/` 实现进行对比
- 检查架构文档中引用的每个系统是否有对应的代码
- 验证 Sprint 计划引用的是真实的工作项
---
## 4. 协作评估
对于无法自动验证的项目，**询问用户**：
- "我无法自动验证核心循环游玩是否良好。是否已进行试玩测试？"
- "未找到试玩报告。是否进行了非正式测试？"
- "性能分析数据不可用。是否要运行 `/perf-profile`？"
**切勿对无法验证的项目假设为 PASS。** 将其标记为"需要人工检查"。
---
## 5. 输出判定结果
关卡检查：[当前阶段] → [目标阶段]
日期：[日期] 检查者：gate-check 技能
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.
- 4d ago First seen · 259 lines · 0 tokens per session scan A 80021c2d62c8
gate-check is a skill published in the GitHub repository pixel-cellar/Claude-Code-Game-Studios (325 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,663 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…