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 TraftG/opencode-game-studio --skill team-combatgit clone --depth 1 https://github.com/TraftG/opencode-game-studioWrote 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/traftg/opencode-game-studio/team-combat)<a href="https://agentmods.dev/skills/traftg/opencode-game-studio/team-combat"><img src="https://agentmods.dev/badge/skills/traftg/opencode-game-studio/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.
<a href="https://agentmods.dev/skills/traftg/opencode-game-studio/team-combat"><img src="https://agentmods.dev/badge/skills/traftg/opencode-game-studio/team-combat.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00826 |
| Opus 5.5 | $0.00020 | $0.00330 |
| Sonnet 5.5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- team-combat — 100% identical, 0 lines differ
- team-combat — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When this skill is invoked, orchestrate the combat team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Team Composition
- game-designer — Design the mechanic, define formulas and edge cases
- gameplay-programmer — Implement the core gameplay code
- ai-programmer — Implement NPC/enemy AI behavior for the feature
- technical-artist — Create VFX, shader effects, and visual feedback
- sound-designer — Define audio events, impact sounds, and ambient combat audio
- qa-tester — Write test cases and validate the implementation
How to Delegate
Use the Task tool to spawn each team member as a subagent:
subagent_type: game-designer— Design the mechanic, define formulas and edge casessubagent_type: gameplay-programmer— Implement the core gameplay codesubagent_type: ai-programmer— Implement NPC/enemy AI behaviorsubagent_type: technical-artist— Create VFX, shader effects, visual feedbacksubagent_type: sound-designer— Define audio events, impact sounds, ambient audiosubagent_type: qa-tester— Write test cases and validate implementation
Always provide full context in each agent's prompt (design doc path, relevant code files, constraints). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 3 agents can run simultaneously).
Pipeline
Phase 1: Design
Delegate to game-designer:
- Create or update the design document in
design/gdd/covering: mechanic overview, player fantasy, detailed rules, formulas with variable definitions, edge cases, dependencies, tuning knobs with safe ranges, and acceptance criteria - Output: completed design document
Phase 2: Architecture
Delegate to gameplay-programmer (with ai-programmer if AI is involved):
- Review the design document
- Design the code architecture: class structure, interfaces, data flow
- Identify integration points with existing systems
- Output: architecture sketch with file list and interface definitions
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.
- 1mo ago First seen · 75 lines · 50 tokens per session scan A 18625e28937a
team-combat is a skill published in the GitHub repository TraftG/opencode-game-studio (45 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 826 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
qa-plan
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when…
automated-smoke-test
Run an automated smoke test using the godot-mcp server. Launches the project, captures debug output, and checks for errors or crashes.
team-qa
Orchestrate the QA team through a full testing cycle. Coordinates qa-lead (strategy + test plan) and qa-tester (test case writing + bug reporting) to produce a complete QA package for a sprint or feature. Covers: test plan generation, test case writing, smoke check gate, manual QA execution, and sign-off report.
skill-improve
Improve a skill using a test-fix-retest loop. Runs static checks, proposes targeted fixes, rewrites the skill, re-tests, and keeps or reverts based on score change.
dev-story
Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before…