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.
git clone --depth 1 https://github.com/sponticelli/gamedev-claude-pluginsWrote 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/commands/sponticelli/gamedev-claude-plugins/submission-plan)<a href="https://agentmods.dev/commands/sponticelli/gamedev-claude-plugins/submission-plan"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/submission-plan/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/commands/sponticelli/gamedev-claude-plugins/submission-plan"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/submission-plan.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.00010 | $0.01245 |
| Opus 5 | $0.00005 | $0.00622 |
| Sonnet 5 | $0.00002 | $0.00249 |
| Haiku 4.5 | $0.00001 | $0.00125 |
Grade A, and why
submission-plan 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submission Plan Generator
Create a certification submission timeline and plan.
Context Gathering
Before generating the submission plan, understand the project:
Identify Targets
- Which platforms?
- Target release date?
- Simultaneous or staggered release?
- Day-one patch strategy?
Understand Current State
- Development phase?
- Content complete?
- Known blockers?
- Previous certification experience?
Check Resources
- Who handles submissions?
- Testing capacity?
- Platform relationships?
- Budget for certification?
Identify Constraints
- Hard deadlines?
- Marketing commitments?
- Platform launch windows?
- Regional requirements?
Use this context to create realistic plan.
Output Format
# Submission Plan: [Game Title]
## Overview
**Target release:** [Date]
**Platforms:** [List with priority]
**Submission lead:** [Name]
**Strategy:** [Simultaneous/Staggered]
## Platform Summary
| Platform | Target Submit | Expected Result | Release |
|----------|---------------|-----------------|---------|
| [Platform] | [Date] | [Date] | [Date] |
## Timeline
### Visual Timeline
Week -8 -7 -6 -5 -4 -3 -2 -1 0 │ │ │ │ │ │ │ │ │ │ │ │ │ └─Submission────│ │ │ │ │ │ │ │ └─Final fixes───────────│ │ │ │ └─Internal cert testing─────────│ │ RELEASE
### Detailed Timeline
#### [Platform 1]
| Milestone | Date | Owner | Deliverables |
|-----------|------|-------|--------------|
| Code complete | [Date] | [Who] | Final build |
| Content complete | [Date] | [Who] | All assets |
| Internal cert 1 | [Date] | [Who] | Test report |
| Fix period | [Date-Date] | [Who] | Bug fixes |
| Internal cert 2 | [Date] | [Who] | Verification |
| Prepare submission | [Date] | [Who] | Package ready |
| Submit | [Date] | [Who] | Submitted |
| Review period | [Date-Date] | - | Awaiting result |
| Response window | [Date-Date] | [Who] | Handle feedback |
| Expected pass | [Date] | - | Certification |
| Resubmit buffer | [Date] | [Who] | If needed |
| Release | [Date] | [Who] | Launch |
[Repeat for each platform]
## Submission Package Preparation
### Build Requirements
| Item | Status | Owner | Due |
|------|--------|-------|-----|
| Final build | [Status] | [Who] | [Date] |
| Build notes | [Status] | [Who] | [Date] |
| Known issues doc | [Status] | [Who] | [Date] |
| Test credentials | [Status] | [Who] | [Date] |
### Documentation
| Document | Status | Owner | Due |
|----------|--------|-------|-----|
| Game description | [Status] | [Who] | [Date] |
| Feature list | [Status] | [Who] | [Date] |
| Network features | [Status] | [Who] | [Date] |
| Privacy policy | [Status] | [Who] | [Date] |
### Assets
| Asset | Status | Owner | Due |
|-------|--------|-------|-----|
| Store icons | [Status] | [Who] | [Date] |
| Screenshots | [Status] | [Who] | [Date] |
| Trailer | [Status] | [Who] | [Date] |
| Key art | [Status] | [Who] | [Date] |
## Risk Assessment
| Risk | Probability | Impact | Mitigation |
|------|-------------|--------|------------|
| Save system issues | [H/M/L] | [H/M/L] | [Action] |
| Network failures | [H/M/L] | [H/M/L] | [Action] |
| Late content | [H/M/L] | [H/M/L] | [Action] |
| Platform delays | [H/M/L] | [H/M/L] | [Action] |
## Contingency Plans
### If First Submission Fails
**Available time:** [Days for resubmit]
**Priority process:** [How to fast-track fixes]
**Resubmission target:** [Date]
### If Multiple Resubmissions Needed
**Impact on release:** [What changes]
**Communication plan:** [How to handle]
**Maximum delay:** [How late can we go]
## Team Responsibilities
| Role | Person | Responsibilities |
|------|--------|------------------|
| Submission lead | [Name] | Overall coordination |
| QA lead | [Name] | Testing, bug triage |
| Dev lead | [Name] | Fix implementation |
| Producer | [Name] | Stakeholder comms |
| Platform contact | [Name] | Platform relationship |
## Communication Plan
### Internal Updates
- Daily standups during cert period
- Issue tracker for all cert bugs
- Slack channel for cert team
### External Updates
- Platform: [How/when to communicate]
- Publisher: [How/when to update]
- Marketing: [Launch readiness updates]
## Success Criteria
### For Submission
- [ ] All blockers fixed
- [ ] Internal cert passed
- [ ] All materials ready
- [ ] Team available for response
### For Launch
- [ ] Certification passed
- [ ] Day-one patch ready (if applicable)
- [ ] Store pages live
- [ ] Marketing aligned
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 · 177 lines · 10 tokens per session scan A a05a10f40658
submission-plan is a command published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 8mo ago), licensed MIT. It adds 10 tokens to every session and 1,245 once invoked, about $0.0001 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-30.
Other commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
status
Show 3d-design team status and recent activity.
unity-optimize
Profile and optimize performance — uses MCP profiler for frame timing, memory, rendering stats. Identifies bottlenecks and applies fixes.