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 studio-project-intakegit 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/studio-project-intake)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/studio-project-intake"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/studio-project-intake.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.1 | $0.00039 | $0.00987 |
| Opus 5 | $0.00019 | $0.00494 |
| Sonnet 5 | $0.00008 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00099 |
Grade A, and why
studio-project-intake 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 today.
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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Studio Project Intake
Overview
Turn an ambiguous game-studio request into a bounded task packet before implementation or diagnosis begins.
When to use
Use for new repositories, new sessions, cross-subsystem work, unclear ownership, risky changes, or tasks mentioning Unity, Lua, C++, services, databases, generated data, or external projects.
When NOT to use
Do not repeat full intake when a current task packet already has verified scope and the request is a micro-change inside that scope.
Required inputs and context discovery
Collect goal, user-visible success, workspace and nested Git roots, branch and dirty state per repository, engine/version, runtime topology, exact subsystem, risk tier, owners, dependencies, generated and excluded paths, do-not-touch paths, available commands, optional code-intelligence provider/version/index freshness, and blocked capabilities. For that optional lane, record provider/version, repository/revision/worktree binding, index state, capability, required languages, artifacts, side effects, and blocker.
Safety and risk level
Intake is read-only. Inspect status and structure without starting services, opening editors, importing databases, or modifying project files.
Workflow
- Identify the requested outcome and the smallest repository boundary that can deliver it. Completion criterion: the goal and excluded scope are one sentence each.
- Inspect Git status, applicable instructions, project maps, manifests, and relevant subsystem entry points. Completion criterion: current state and ownership risks are captured without mutation.
- Classify risk as read-only, low, medium, or high and list forbidden actions. Completion criterion: each planned side effect has an approval and rollback requirement.
- Record engine/version, services, ports, database/schema, generated-source relationships, and test commands only when verified. Completion criterion: snapshots are separated from hypotheses.
- Select the next workflow skill and, for verified multi-repository work, include a conservative project-profile draft with unknown owners and commands labeled.
Completion criterion: the task packet is executable without rediscovery and routes through
studio-workspace-routingwhen applicable. - The graph lane is optional. Apply
code-intelligence-contractonly when graph context or capability is requested or materially useful for scoped intake; provider existence alone never triggers it. Pure intake remains intake, and the optional graph lane may stay absent or BLOCKED without failing intake; intake may still succeed when the graph lane is BLOCKED because intake owns scope discovery, not a graph verdict. Completion criterion: the packet records provider/version, repository/revision/worktree binding, index state, capability, required languages, artifacts, side effects, and blocker while keeping graph extraction separate from source/runtime verification.
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.
- today Changed · +2 lines c2bbfac5792d
- 7d ago First seen · 78 lines · 39 tokens per session scan A 3dfa6e8b2824
studio-project-intake is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 987 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.