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 commands/sponticelli/gamedev-claude-plugins/deploy-checklistgit 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/deploy-checklist)<a href="https://agentmods.dev/commands/sponticelli/gamedev-claude-plugins/deploy-checklist"><img src="https://agentmods.dev/badge/commands/sponticelli/gamedev-claude-plugins/deploy-checklist.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.00010 | $0.01048 |
| Opus 5 | $0.00005 | $0.00524 |
| Sonnet 5 | $0.00002 | $0.00210 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
deploy-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 6d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deployment Checklist Generator
Generate a comprehensive deployment checklist tailored to the release type and platform.
Context Gathering
Before generating, understand:
Release Context
- Release type (major, minor, patch, hotfix)
- Target platforms (Steam, Console, Mobile, Web)
- New features or changes included
- Database migrations required
Team Context
- Release owner
- On-call personnel
- Communication channels
Output Format
# Deployment Checklist: v[Version]
## Release Overview
**Version:** [X.Y.Z]
**Type:** [Major/Minor/Patch/Hotfix]
**Date:** [Scheduled date/time UTC]
**Owner:** [Name]
**On-Call:** [Name]
---
## Pre-Deployment (T-24h to T-1h)
### Code Readiness
- [ ] All features merged to release branch
- [ ] Code freeze in effect
- [ ] No critical bugs in release
- [ ] Release notes drafted
### QA Sign-Off
- [ ] Smoke tests passed
- [ ] Regression tests passed
- [ ] Platform-specific tests passed
- [ ] QA lead has signed off
### Build Readiness
- [ ] Release build created
- [ ] Build version matches release
- [ ] Artifact stored and accessible
- [ ] Build tested on target platforms
### Database
- [ ] Migrations tested on staging
- [ ] Rollback scripts prepared
- [ ] Backup scheduled
- [ ] Data integrity verified
### Feature Flags
- [ ] New features flagged OFF by default
- [ ] Flag configurations reviewed
- [ ] Rollback flags identified
### Communication
- [ ] Team notified of deployment window
- [ ] Support team briefed on changes
- [ ] Player announcement drafted
- [ ] Status page ready
---
## Deployment (T-0)
### Start Deployment
- [ ] Announce deployment starting in #releases
- [ ] Set status page to "Deploying"
- [ ] Begin deployment procedure
### Platform-Specific
#### Steam
- [ ] Upload to Steam depot
- [ ] Set build live on branch
- [ ] Verify SteamDB shows update
- [ ] Wait for CDN propagation (~15 min)
#### Console (if applicable)
- [ ] Certification passed
- [ ] Submit to platform
- [ ] Coordinate regional timing
#### Mobile (if applicable)
- [ ] iOS: Submit for review or release
- [ ] Android: Set rollout percentage
- [ ] Monitor for review issues
#### Web (if applicable)
- [ ] Deploy to CDN
- [ ] Invalidate cache
- [ ] Verify version endpoint
### Database Migrations
- [ ] Run migrations
- [ ] Verify migration success
- [ ] Spot-check data integrity
### Feature Flag Activation
- [ ] Enable flags per rollout plan
- [ ] Verify flag states
---
## Post-Deployment (T+0 to T+4h)
### Immediate Verification
- [ ] Application starts successfully
- [ ] Login flow works
- [ ] Core gameplay functional
- [ ] No error spikes in logs
### Metrics Check
- [ ] Error rate normal (< [X]%)
- [ ] Latency normal (< [X]ms)
- [ ] Player count recovering
- [ ] No crash spikes
### Smoke Test
- [ ] New player flow
- [ ] Returning player flow
- [ ] Purchase flow (if applicable)
- [ ] Key features working
### Communication
- [ ] Update status page to "Deployed"
- [ ] Announce deployment complete
- [ ] Publish patch notes
- [ ] Notify support team
---
## Monitoring Period (T+4h to T+24h)
### Extended Monitoring
- [ ] Review error logs
- [ ] Check player feedback channels
- [ ] Monitor support tickets
- [ ] Watch revenue metrics (if applicable)
### Issue Triage
- [ ] Assess any reported issues
- [ ] Determine if hotfix needed
- [ ] Document known issues
---
## Rollback Procedure (If Needed)
### Triggers for Rollback
- Crash rate > [X]%
- Error rate > [X]%
- Revenue impact > [X]%
- Critical exploit discovered
### Rollback Steps
1. [ ] Announce rollback in #incidents
2. [ ] Disable new feature flags
3. [ ] Deploy previous version
4. [ ] Verify rollback successful
5. [ ] Update status page
6. [ ] Communicate to players
7. [ ] Schedule postmortem
---
## Sign-Off
### Deployment Complete
- [ ] All verification passed
- [ ] Monitoring shows stable
- [ ] Release owner sign-off
- [ ] Handoff to on-call complete
### Post-Deployment
- [ ] Update release log
- [ ] Close deployment ticket
- [ ] Schedule retrospective (if issues)
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.
- 6d ago First seen · 196 lines · 10 tokens per session scan A 918ec5782a49
deploy-checklist is a command published in the GitHub repository sponticelli/gamedev-claude-plugins (15 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 1,048 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
Command "release-plan" from alisunstar/OpenSunstar, covering /rd:release-plan — 发布计划, 先读, 执行, 产物 and 人工确认.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.