cgs-bug-report

cgs-bug-report is a skill for Claude Code from merlinhu1/codex-game-studio. It costs 48 tokens per session (582 once invoked), scanned A, original, MIT.

A structured record of a reproducible software bug, including the environment, steps, expected and actual behavior, severity, evidence, and owner.

In plain words
What is it for?
Use it to report game bugs with reproduction steps, logs, screenshots, recordings, failing tests, likely ownership, and a verification path.
Why use it?
It gives another developer enough information to see the same problem and understand its impact.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: model in frontmatter; reads .claude/ paths; installed under .agents/ (shared by several agents).

Good fit Use it to report game bugs with reproduction steps, logs, screenshots, recordings, failing tests, likely ownership, and a verification path.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/merlinhu1/codex-game-studio/cgs-bug-report
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-bug-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.

agentmods badge for cgs-bug-report

README.md
[![agentmods](https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-bug-report/github.svg)](https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-bug-report)
Your own site
<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-bug-report"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-bug-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.

agentmods 80×15 button for cgs-bug-report

Your own site · 80×15
<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-bug-report"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-bug-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00582
Opus 5 $0.00024 $0.00291
Sonnet 5 $0.00010 $0.00116
Haiku 4.5 $0.00005 $0.00058

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

Security

Grade A, and why

cgs-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 9d 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-bug-report/SKILL.md · 82 lines

What it actually says

Codex Game Studio Bug Report

Use this skill for bug report work in Template Game.

Objective

Capture a reproducible bug with environment, steps, expected/actual behavior, severity, evidence, and owner.

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

  1. Capture environment, build/version, branch, and affected feature.
  2. Write Reproduction Steps that a different agent can follow without extra context.
  3. Record Expected vs Actual behavior and player impact.
  4. Attach Evidence such as logs, screenshots, recordings, failing tests, or engine output.
  5. Assign severity, likely owner role, regression risk, and verification path.

Write Targets

  • tests/
  • production/session-state/
  • prototypes/

Output Contract

  • Summary
  • Reproduction Steps
  • Expected vs Actual
  • Evidence
  • Severity
  • Risks
  • Changed files or proposed files
  • Verification evidence
  • Next owner or decision

Quality Gates

  • Reproduction Steps
  • Expected vs Actual
  • Evidence
  • Severity
  • 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.

  1. 9d ago First seen · 82 lines · 48 tokens per session scan A f000f709f749

Subscribe to this mod's changes

cgs-bug-report is a skill published in the GitHub repository merlinhu1/codex-game-studio (53 stars, last pushed 1mo ago), licensed MIT. It adds 48 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.

Related

Other skills, from other repositories

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

temporal-python-testing

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

HermeticOrmus/claude-code-game-development · 45 tokens

console-get-logs

Retrieve Unity Editor logs from the MCP plugin's LogCollector, optionally filtered by log type or time window. Useful for debugging and monitoring Editor activity.

IvanMurzak/Unity-MCP · 35 tokens

editor-application-get-state

Return the current state of UnityEditor.EditorApplication — playmode, paused state, compilation state, and related flags.

IvanMurzak/Unity-MCP · 31 tokens