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 hoatv2211/GameStudio-CodexKIT --skill game-feature-brainstorminggit clone --depth 1 https://github.com/hoatv2211/GameStudio-CodexKITWrote 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/hoatv2211/gamestudio-codexkit/game-feature-brainstorming)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/game-feature-brainstorming"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/game-feature-brainstorming/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/hoatv2211/gamestudio-codexkit/game-feature-brainstorming"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/game-feature-brainstorming.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.00038 | $0.00756 |
| Opus 5 | $0.00019 | $0.00378 |
| Sonnet 5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
game-feature-brainstorming 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Game Feature Brainstorming
Overview
Clarify the desired player experience, then compare a small set of meaningfully different options before implementation details harden.
When to use
Use for new mechanics, progression, combat, economy, social features, tools, UX flows, or technical approaches with real design trade-offs.
When NOT to use
Do not use when an approved option already needs a formal specification, when the request is a micro-fix, or when safety requires immediate containment rather than ideation.
Required inputs and context discovery
Collect player goal, target audience, platform, session length, constraints, production budget, content burden, technical limits, accessibility needs, success signals, and non-goals.
Safety and risk level
Brainstorming is read-only. It does not authorize prototypes, purchases, schema changes, service work, or asset mutation.
Workflow
- Frame the player problem and the experience the feature should create. Completion criterion: outcome and non-goals are testable statements.
- Identify constraints and the decisions with the highest downstream cost. Completion criterion: technical, content, UX, and production limits are explicit.
- Propose two or three distinct options rather than cosmetic variants. Completion criterion: each option has a different core loop or implementation shape.
- Compare player value, complexity, risk, tuning leverage, exploit surface, and testability. Completion criterion: a trade-off table makes the recommendation inspectable.
- Recommend one option and list assumptions requiring prototype or playtest evidence.
Completion criterion: the selected direction can move to
game-feature-to-spec.
Evidence and output contract
Produce problem framing, constraints, two or three options, trade-off table, recommendation, rejected alternatives, assumptions, and required prototype/playtest evidence.
Handoff contract
Record chosen and rejected options, decision rationale, unresolved assumptions, tuning risks, and the prompt for creating the specification.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 79 lines · 38 tokens per session scan A a5c0f08e76df
game-feature-brainstorming is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 756 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-31.
Other skills, from other repositories
deep-discovery
Use when the user asks for deep discovery, 100-question brainstorming, idea interrogation, architecture stress testing, strategy vetting, weakness finding, hole-poking, exhaustive exploration, planning or auditing Codex plugins or skills, or pre-commitment review of a design, plan, strategy, architecture, product…
prewalk
Use when the user wants a coding task executed with a strong planner model first and a faster/cheaper executor model after the first successful implementation edit.
code-standards
C# coding standards and code review. Use when the user mentions coding standards or conventions, writing code to spec, defining standards for a project, cohesion and coupling, design pattern selection, or naming conventions, or wants a code review on the design and standards dimension.
registry-broker-orchestrator
Use Registry Broker to discover and summon specialist agents for focused subtasks from inside Codex.
unity-performance
Unity performance optimization. Use when the user asks to optimize a class, view, function, folder or an entire module, or mentions stutter, lag, frame drops, low FPS, jank, overheating, battery drain, GC allocation, memory leaks, DrawCalls, batching, overdraw, slow loading, large build size, Profiler, PerfDog, or…
sega
A playful, arcade-inspired interface for games — built on the VT323 pixel typeface, hard-edged 0px corners, chunky pill buttons that physically press into solid offset blocks.