cgs-team-combat

cgs-team-combat is a skill for Claude Code from merlinhu1/codex-game-studio. It costs 46 tokens per session (583 once invoked), scanned A, original, MIT.

A cross-team workflow for building and checking game combat. It connects combat design and code with tuning, animation, visual effects, sound, and QA.

In plain words
What is it for?
Use it to define combat goals, tune how attacks feel, coordinate related assets and implementation, and prepare a QA scenario.
Why use it?
Combat changes often affect several disciplines at once. This workflow makes the required handoffs, feedback, and checks explicit.

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 define combat goals, tune how attacks feel, coordinate related assets and implementation, and prepare a QA scenario.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/merlinhu1/codex-game-studio/cgs-team-combat"><img src="https://agentmods.dev/badge/skills/merlinhu1/codex-game-studio/cgs-team-combat.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 583 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.00046 $0.00583
Opus 5 $0.00023 $0.00292
Sonnet 5 $0.00009 $0.00117
Haiku 4.5 $0.00005 $0.00058

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

Security

Grade A, and why

cgs-team-combat 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 6d 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-team-combat/SKILL.md · 80 lines

What it actually says

Codex Game Studio Team Combat

Use this skill for team combat work in Template Game.

Objective

Coordinate combat design, implementation, tuning, animation, VFX, audio, and QA handoffs.

Inputs

  • AGENTS.md
  • .codex/studio.json
  • task-relevant files named by the user or task record
  • design/gdd.md
  • production/timeline.md
  • task-relevant team files

Arguments

  • Objective or user request.
  • Target files, scenes, assets, or docs.
  • Constraints, deadlines, acceptance criteria, and verification command when known.

Procedure

  1. Clarify the requested coordinate combat design, implementation, tuning, animation, vfx, audio, and qa handoffs. and identify the current project stage.
  2. Collect evidence for Combat Goal, Tuning, Feedback.
  3. Coordinate handoffs between disciplines and name each owner, artifact, and validation need.
  4. Produce the requested artifact or review with clear file paths and verification evidence.

Write Targets

  • production/
  • design/

Output Contract

  • Summary
  • Combat Goal
  • Tuning
  • Feedback
  • QA Scenario
  • Risks
  • Changed files or proposed files
  • Verification evidence
  • Next owner or decision

Quality Gates

  • Combat Goal
  • Tuning
  • Feedback
  • QA Scenario
  • 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. 6d ago First seen · 80 lines · 46 tokens per session scan A 9526f19d8c66

Subscribe to this mod's changes

cgs-team-combat is a skill published in the GitHub repository merlinhu1/codex-game-studio (54 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 583 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-09-03.

Related

Other skills, from other repositories

gate-check

Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.

striderZA/OpenCodeGameStudios · 64 tokens

godot-project-management

Domain skill — Return project metadata, version, viewport, and autoloads. Return a filtered recursive project file tree. Search project files by glob or name fragment. Read project settings by prefix or key. Set and persist one project setting. Convert a Godot resource UID to res:// path. Convert a res:// resource…

dcc-mcp/dcc-mcp-godot · 76 tokens

init-template

First-time repo setup for new projects. Transforms the cloned OCGS template into a clean, ready-to-use game project with your own identity.

striderZA/OpenCodeGameStudios · 33 tokens

launch-checklist

Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

TraftG/opencode-game-studio · 33 tokens

milestone-review

Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.

TraftG/opencode-game-studio · 40 tokens

project-stage-detect

Automatically analyze project state, detect stage, identify gaps, and recommend next steps based on existing artifacts. Use when user asks 'where are we in development', 'what stage are we in', 'full project audit'.

striderZA/OpenCodeGameStudios · 48 tokens