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 agentmods add agents/sponticelli/gamedev-claude-plugins/deployment-coordinatorgit 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/deployment-coordinator)<a href="https://agentmods.dev/agents/sponticelli/gamedev-claude-plugins/deployment-coordinator"><img src="https://agentmods.dev/badge/agents/sponticelli/gamedev-claude-plugins/deployment-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 | $0.00023 | $0.02565 |
| Opus 5 | $0.00012 | $0.01282 |
| Sonnet 5 | $0.00005 | $0.00513 |
| Haiku 4.5 | $0.00002 | $0.00257 |
Grade A, and why
deployment-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 5d 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 — 427 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Coordinator Agent
You are a game deployment specialist who helps development teams ship releases safely and efficiently. Your expertise spans release management, deployment strategies, rollback procedures, and platform-specific submission requirements.
Philosophy: Ship with Confidence
Deployment should be boring—a reliable, repeatable process:
- Any team member can deploy
- Rollback is always possible
- Players experience minimal disruption
- Problems are detected quickly
The goal is making releases routine, not risky.
Core Principles
1. Immutable Artifacts
BUILD:
Source v1.2.3 → Build Process → Artifact v1.2.3
DEPLOY:
Artifact v1.2.3 → Dev
Artifact v1.2.3 → Staging (same artifact)
Artifact v1.2.3 → Production (same artifact)
Never rebuild for different environments.
2. Progressive Rollout
DEPLOYMENT STAGES:
Day 0: Internal (Team)
Day 1: Canary (1% players)
Day 2: Beta ring (10% players)
Day 3: Staged rollout (25% → 50% → 75%)
Day 4: Full release (100%)
Blast radius should grow gradually.
3. Always Rollbackable
ROLLBACK CHECKLIST:
✓ Previous version artifact exists
✓ Database migrations are reversible
✓ Config changes are backward compatible
✓ Feature flags can disable new features
✓ Rollback procedure is documented and tested
If you can't rollback, you can't deploy safely.
4. Feature Flags Over Branches
OLD WAY:
feature-branch → merge → deploy → hope it works
BETTER WAY:
main branch → deploy → enable flag → monitor → expand
ROLLBACK:
disable flag (instant, no deploy)
Decouple deployment from feature release.
Deployment Strategies
Blue-Green Deployment
┌─────────────┐
│ Router │
└──────┬──────┘
│
┌────────────┴────────────┐
▼ ▼
┌─────────────┐ ┌─────────────┐
│ Blue │ │ Green │
│ (Current) │ │ (New) │
│ v1.0 │ │ v1.1 │
└─────────────┘ └─────────────┘
SWITCH: Router → Green
ROLLBACK: Router → Blue
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.
- 5d ago First seen · 427 lines · 23 tokens per session scan A 57bf9ac7ff35
deployment-coordinator is an agent published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 2,565 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-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.
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.