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-handoffgit 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-handoff)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/studio-handoff"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/studio-handoff.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.00057 | $0.00851 |
| Opus 5 | $0.00028 | $0.00426 |
| Sonnet 5 | $0.00011 | $0.00170 |
| Haiku 4.5 | $0.00006 | $0.00085 |
Grade A, and why
studio-handoff 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 7d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Studio Handoff
Overview
Create a restartable state transfer that distinguishes verified work from snapshots, hypotheses, and blockers.
When to use
Use when a session ends, ownership changes, work becomes blocked, a subsystem crosses teams, or another agent must continue without repeating discovery.
When NOT to use
Do not create a handoff as a substitute for running available verification or resolving a small task that can be completed safely now.
Required inputs and context discovery
Collect repository/path, branch, goal, owned and excluded scope, current Git state, files touched, commands run, artifacts, decisions, failures, open hypotheses, dependencies, and next actions.
Safety and risk level
Writing a handoff is low-risk. Preserve existing project handoff conventions, never expose credentials, and never rewrite unrelated history or other sessions’ ownership.
Workflow
- Re-read the task packet, applicable instructions, and current Git status. Completion criterion: the handoff reflects current state rather than memory.
- List files touched and commands run with exact results. Completion criterion: every PASS claim maps to fresh evidence.
- Separate Verified, Snapshot, Unverified, and BLOCKED facts. Completion criterion: no hypothesis appears under Verified.
- Record failures, decisions, ownership boundaries, and do-not-touch paths. Completion criterion: the next session can avoid conflicting or unsafe work.
- Provide three to seven ordered next actions and a reactivation prompt. Completion criterion: another session can start with one bounded command or inspection.
Evidence and output contract
Produce HANDOFF.md with repository/path, branch, goal, scope ownership/do-not-touch, files touched, commands/tests, Verified results, Snapshot assumptions, Unverified hypotheses, BLOCKED items, failures, decisions, next actions, and Reactivation prompt.
Handoff contract
The output is the handoff contract. Keep exact paths, symbols, ports, error strings, and commands intact; sanitize secrets and raw credentials.
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.
- 7d ago First seen · 83 lines · 57 tokens per session scan A 14316b621103
studio-handoff is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed yesterday), licensed MIT. It adds 57 tokens to every session and 851 once invoked, about $0.0003 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.
registry-broker-orchestrator
Use Registry Broker to discover and summon specialist agents for focused subtasks from inside Codex.
codex-sdd:customize
Guide for injecting custom MCP tools, skills, and hook points into the OpenSpec workflow for team-specific processes.
codex-sdd:archive
Preserve change artifacts (proposal, design, tasks) into structured archive and update knowledge base. Final phase of OpenSpec workflow.
codex-sdd:plan
Create design.md with technical architecture and tasks.md with executable breakdown from an approved proposal. Second phase of OpenSpec workflow.