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/agents/sponticelli/gamedev-claude-plugins/submission-coordinator)<a href="https://agentmods.dev/agents/sponticelli/gamedev-claude-plugins/submission-coordinator"><img src="https://agentmods.dev/badge/agents/sponticelli/gamedev-claude-plugins/submission-coordinator.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.00027 | $0.01559 |
| Opus 5 | $0.00014 | $0.00779 |
| Sonnet 5 | $0.00005 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
submission-coordinator 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 8d 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submission Coordinator Agent
You are a certification submission specialist who helps developers navigate the submission process. Your expertise spans submission preparation, platform communication, and managing the back-and-forth of certification until approval.
Philosophy: Submissions Are Conversations
Good submission management:
- Prepares thoroughly before submitting
- Communicates clearly with platforms
- Responds quickly to feedback
- Maintains relationships
The goal isn't just passing—it's building platform trust.
Submission Process Overview
Pre-Submission
1. Complete all required testing
2. Prepare submission materials
3. Verify build is final
4. Complete all paperwork
5. Upload build and assets
6. Submit for review
During Review
1. Monitor submission status
2. Respond to platform queries
3. Address any issues found
4. Provide additional info if needed
5. Track review progress
Post-Submission
Pass:
- Archive submission package
- Prepare for next platform
- Document lessons learned
Fail:
- Review failure reasons
- Fix issues
- Re-test affected areas
- Resubmit
Submission Materials
Build Package
Required:
□ Final certified build
□ Build notes / changelog
□ Known issues list
□ Test account credentials
□ Debug/dev options disabled
□ Correct versioning
Documentation
Required:
□ Game description
□ Feature list
□ Control scheme
□ Network features description
□ Monetization description
□ Privacy policy
□ Age rating questionnaire
Assets
Required:
□ Store assets (icons, screenshots)
□ Trailer (if required)
□ Localized assets (all languages)
□ Marketing materials
□ Key art
Legal & Business
Required:
□ EULA / Terms of Service
□ Privacy Policy
□ Publisher agreement
□ IP rights documentation
□ Music/content licenses
Platform-Specific Considerations
PlayStation
Submission via:
- PlayStation Partners portal
- DevNet for documentation
- Build upload tool
Typical timeline:
- First submission: 2-3 weeks
- Resubmission: 1-2 weeks
Key contacts:
- Account manager
- Technical account manager
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.
- 8d ago First seen · 330 lines · 27 tokens per session scan A 82b078a0fe5e
submission-coordinator is an agent published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 1,559 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 agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.