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 store-submission-checklistgit 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/store-submission-checklist)<a href="https://agentmods.dev/skills/hoatv2211/gamestudio-codexkit/store-submission-checklist"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/store-submission-checklist/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/store-submission-checklist"><img src="https://agentmods.dev/badge/skills/hoatv2211/gamestudio-codexkit/store-submission-checklist.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.00040 | $0.00856 |
| Opus 5 | $0.00020 | $0.00428 |
| Sonnet 5 | $0.00008 | $0.00171 |
| Haiku 4.5 | $0.00004 | $0.00086 |
Grade A, and why
store-submission-checklist 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 10d 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.
Store Submission Checklist
Overview
Prepare an evidence-backed storefront submission package while keeping account actions, legal attestations, payments, signing, and final submission human-controlled.
When to use
Use for platform package readiness, metadata review, age ratings, privacy declarations, entitlements, achievements, commerce, localization, screenshots, and certification checklists.
When NOT to use
Do not use to log into a store account, accept legal terms, spend money, sign binaries, upload packages, or press submit without explicit human approval for that exact action.
Required inputs and context discovery
Collect platform and program version, requirement source and date, account owner, candidate package hash, release preflight, metadata, assets, supported languages, ratings, privacy disclosures, commerce behavior, entitlements, test accounts, waivers, and submission window.
Safety and risk level
High-risk external publication. Checklist work is read-only; credentials remain outside artifacts. Any account mutation, upload, legal attestation, fee, signing, or submission is BLOCKED until explicit human approval and a platform-specific dry run exist.
Workflow
- Bind the checklist to a platform, current requirement source, account owner, and candidate hash.
Completion criterion: stale or ambiguous requirements are
BLOCKED. - Review package, metadata, assets, localization, ratings, privacy, commerce, and entitlement requirements. Completion criterion: every applicable item has evidence, owner, and status.
- Validate platform test results, known issues, waivers, and review notes. Completion criterion: exceptions name the authorized approver and expiry.
- Prepare an exact submission dry run without authenticating or uploading. Completion criterion: fields, files, hashes, order, and expected confirmations are documented.
- Request human approval for the exact external action.
Completion criterion: without approval, final status remains
BLOCKED; this skill never performs submission.
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.
- 10d ago First seen · 79 lines · 40 tokens per session scan A 40f73c75c884
store-submission-checklist is a skill published in the GitHub repository hoatv2211/GameStudio-CodexKIT (3 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 856 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.
registry-broker-orchestrator
Use Registry Broker to discover and summon specialist agents for focused subtasks from inside Codex.
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.
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.