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/bug-reportnpx skills add pixel-cellar/Claude-Code-Game-Studios --skill bug-reportgit 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/bug-report)<a href="https://agentmods.dev/skills/pixel-cellar/claude-code-game-studios/bug-report"><img src="https://agentmods.dev/badge/skills/pixel-cellar/claude-code-game-studios/bug-report.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.00046 | $0.00737 |
| Opus 5 | $0.00023 | $0.00368 |
| Sonnet 5 | $0.00009 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
bug-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 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.
What it actually says
当通过描述调用时：
-
解析描述，提取关键信息。
-
搜索代码库，使用 Grep/Glob 查找相关文件以补充上下文。
-
生成缺陷报告：
# 缺陷报告 (Bug Report)
## 概述 (Summary)
**标题**: [简洁、描述性的标题]
**ID**: BUG-[NNNN]
**严重程度 (Severity)**: [S1-严重 / S2-主要 / S3-次要 / S4-微小]
**优先级 (Priority)**: [P1-立即 / P2-下一迭代 / P3-待办 / P4-愿望清单]
**状态**: Open
**报告日期**: [日期]
**报告人**: [姓名]
## 分类 (Classification)
- **类别**: [玩法 / UI / 音频 / 视觉 / 性能 / 崩溃 / 网络]
- **系统**: [受影响的游戏系统]
- **频率**: [总是 / 经常 (>50%) / 有时 (10-50%) / 罕见 (<10%)]
- **回归 (Regression)**: [是/否/未知 —— 之前是否正常工作？]
## 环境 (Environment)
- **构建版本**: [版本号或 commit hash]
- **平台**: [操作系统、硬件（如相关）]
- **场景/关卡**: [游戏中的位置]
- **游戏状态**: [相关状态 —— 背包、任务进度等]
## 复现步骤 (Reproduction Steps)
**前置条件**: [开始前所需的状态]
1. [具体步骤 1]
2. [具体步骤 2]
3. [具体步骤 3]
**预期结果**: [应该发生什么]
**实际结果**: [实际发生了什么]
## 技术上下文 (Technical Context)
- **可能受影响的文件**: [基于代码库搜索的文件列表]
- **关联系统**: [可能涉及的其他系统]
- **可能的根本原因**: [如果从描述中可识别]
## 证据 (Evidence)
- **日志**: [相关日志输出（如有）]
- **视觉证据**: [视觉证据的描述]
## 关联问题 (Related Issues)
- [关联缺陷或设计文档的链接]
## 备注 (Notes)
[任何额外的上下文或观察]
当使用 analyze 调用时：
- 读取目标文件。
- 识别潜在缺陷：空引用（null reference）、差一错误（off-by-one error）、竞态条件（race condition）、未处理的边界情况、资源泄漏、不正确的状态转换。
- 针对每个潜在缺陷，生成一份缺陷报告，包含可能的触发场景和修复建议。
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 · 73 lines · 46 tokens per session scan A be5a7a4c4852
bug-report is a skill published in the GitHub repository pixel-cellar/Claude-Code-Game-Studios (325 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 737 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.
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…