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 MRCalderon3D/everything-game-dev-code --skill store-submissiongit clone --depth 1 https://github.com/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/store-submission)<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/store-submission"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/store-submission/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/mrcalderon3d/everything-game-dev-code/store-submission"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/store-submission.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.00020 | $0.00328 |
| Opus 5.5 | $0.00008 | $0.00131 |
| Sonnet 5.5 | $0.00004 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
store-submission 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 14d 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.
What it actually says
Store Submission
Purpose
Prepare store-facing assets, metadata, compliance paperwork, and packaging details for submission.
Use When
- approaching launch or major update submission
- store requirements are not yet consolidated
- platform and marketing dependencies are diverging
Inputs
- release candidate build
- store requirements
- screenshots and metadata
- age rating and legal needs
Process
- build a submission checklist for each platform/store
- validate asset and metadata completeness
- check versioning, entitlement, and region requirements
- coordinate with localization and support information
- track platform-specific blockers through submission
Outputs
- store submission checklist
- metadata package
- asset-completeness report
- submission blocker list
Quality Bar
- turns risk into explicit evidence and ownership
- keeps release blockers visible instead of implicit
- connects quality decisions to milestone and platform impact
Common Failure Modes
- severity inflation or minimization without player-impact context
- treating waived risks as invisible
- submission checklists that are incomplete or stale
Related Agents
- release-manager
- producer
- doc-updater
Related Commands
- release-check
- patch-notes
- cert-check
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
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.
- 14d ago First seen · 60 lines · 20 tokens per session scan A cb1f3e0c6115
store-submission is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (98 stars, last pushed 15d ago), licensed MIT. It adds 20 tokens to every session and 328 once invoked, about $0.0001 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-10-10.
Other skills, from other repositories
balance-check
Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
godot-build-optimization
Analyze a Godot project and generate a version-aware SCons export-template profile, optional .gdbuild feature profile, and reproducible artifact-size report. Use when reducing packaged engine size before export; keep runtime validation and risky binary post-processing explicit.
cgs-adopt
Use for adopt tasks that inventory existing source, assets, docs, and tests before mapping work into CGS structure; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-brainstorm
Use for brainstorm tasks that explore the game idea with player fantasy, verbs, pillars, audience, constraints, and scope tiers; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-bug-report
Use for bug report tasks that capture a reproducible bug with environment, steps, expected/actual behavior, severity, evidence, and owner; produce verification evidence, changed or proposed files, and handoff boundaries.