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/latestaiagents/agent-skills/deploy-checklistgit clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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/latestaiagents/agent-skills/deploy-checklist)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/deploy-checklist"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/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.00011 | $0.01277 |
| Opus 5 | $0.00005 | $0.00639 |
| Sonnet 5 | $0.00002 | $0.00255 |
| Haiku 4.5 | $0.00001 | $0.00128 |
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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/deploy-checklist
Comprehensive deployment checklist with automated verification and rollback preparation.
What I Need
Tell me:
- What are you deploying? (service name, version)
- Target environment (prod/staging)
- Deployment method (rolling/blue-green/canary)
Pre-Deployment Checklist
┌─────────────────────────────────────────────────────────────┐
│ PRE-DEPLOYMENT CHECKLIST │
│ Service: api-service v2.3.4 │
│ Environment: production │
├─────────────────────────────────────────────────────────────┤
│ │
│ 📋 REQUIREMENTS │
│ ✓ Code reviewed and approved │
│ ✓ Tests passing (unit: 342/342, integration: 89/89) │
│ ✓ Security scan clean (0 high, 2 medium - acknowledged) │
│ ✓ Staging deployment successful │
│ ✓ QA sign-off received │
│ │
│ 🚫 BLOCKERS CHECK │
│ ✓ No active incidents (checked PagerDuty) │
│ ✓ No change freeze active │
│ ✓ Not during peak hours (current: 2.3k RPM, peak: 10k) │
│ ✓ On-call engineer available (@jane) │
│ │
│ 📊 BASELINE METRICS (capture before deploy) │
│ • Error rate: 0.08% │
│ • P50 latency: 45ms │
│ • P99 latency: 230ms │
│ • Active connections: 1,247 │
│ • Memory usage: 67% │
│ • CPU usage: 34% │
│ │
│ 🔙 ROLLBACK PREPARATION │
│ ✓ Previous version available: v2.3.3 │
│ ✓ Rollback command ready: │
│ kubectl rollout undo deployment/api-service │
│ ✓ Rollback tested in staging: Yes │
│ ✓ Database migrations: Backward compatible ✓ │
│ │
│ 📢 COMMUNICATION │
│ ✓ #deployments channel notified │
│ ✓ Status page: No maintenance needed │
│ □ Customer notification: Not required │
│ │
└─────────────────────────────────────────────────────────────┘
All checks passed. Ready to deploy? [y/N]
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 · 131 lines · 11 tokens per session scan A 2f30555b6a70
deploy-checklist is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 4mo ago), licensed MIT. It adds 11 tokens to every session and 1,277 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-31.
Other commands, from other repositories
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).
fw-setup-troubleshoot
Diagnose FDK / nvm / shell PATH; optional --fix runs automated repair Task; on failure switches to interactive human-guided SOP mode.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.