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 skills/misonl/ling/deployment-proceduresnpx skills add MisonL/Ling --skill deployment-proceduresgit clone --depth 1 https://github.com/MisonL/LingWhat 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.00036 | $0.01767 |
| Opus 5 | $0.00018 | $0.00883 |
| Sonnet 5 | $0.00007 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
deployment-procedures 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 3d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
部署规程
生产环境发布的部署原则与决策逻辑。 学习如何思考（THINK），而非死记硬背脚本。
[WARN] 如何使用此技能
此技能传授的是部署原则，不是可盲目复制的脚本。
- 每次部署都有差异
- 理解每一步背后的原因
- 根据平台实际情况调整流程
1. 平台选择
决策树
What are you deploying?
|
+-- Static site / JAMstack
| +-- Vercel, Netlify, Cloudflare Pages
|
+-- Simple web app
| +-- Managed -> Railway, Render, Fly.io
| +-- Control -> VPS + PM2/Docker
|
+-- Microservices
| +-- Container orchestration
|
+-- Serverless
+-- Edge functions, Lambda
不同平台有不同规程
| 平台 | 部署方式 |
|---|---|
| Vercel/Netlify | Git push（代码推送）自动部署 |
| Railway/Render | Git push 或 CLI |
| VPS + PM2 | SSH + 手动步骤 |
| Docker | 镜像推送 + 编排 |
| Kubernetes | kubectl apply |
2. 部署前原则
四大验证类别
| 类别 | 检查项 |
|---|---|
| 代码质量 | 测试通过、Lint 清理完成、已评审 |
| 构建（Build） | 生产构建成功、无告警 |
| 环境 | 环境变量已设置、凭据已更新 |
| 安全性 | 已备份、回滚方案就绪 |
部署前检查清单
- 所有测试通过
- 代码已评审并批准
- 生产构建成功
- 环境变量已核验
- 数据库迁移已就绪（如有）
- 回滚方案已记录
- 已通知团队
- 监控已就绪
3. 部署工作流原则
5 阶段流程
1. PREPARE
+-- Verify code, build, env vars
2. BACKUP
+-- Save current state before changing
3. DEPLOY
+-- Execute with monitoring open
4. VERIFY
+-- Health check, logs, key flows
5. CONFIRM or ROLLBACK
+-- All good? Confirm. Issues? Rollback.
阶段原则
| 阶段 | 原则 |
|---|---|
| 准备 | 绝不部署未经测试的代码 |
| 备份 | 没有备份就无法回滚 |
| 部署 | 观察过程，不要中途走开 |
| 验证 | 宁可怀疑，务必验证 |
| 确认 | 随时准备触发回滚 |
4. 部署后验证
验证内容
| 检查项 | 为什么要查 |
|---|---|
| 健康端点（Health） | 确认服务正常运行 |
| 错误日志 | 确认无新增错误 |
| 核心业务流 | 确保关键功能正常 |
| 性能 | 响应时间可接受 |
验证时间窗口
- 首个 5 分钟：主动监控
- 15 分钟：确认稳定
- 1 小时：最终验证
- 次日：复审指标
5. 回滚原则
何时回滚
| 现象 | 行动建议 |
|---|---|
| 服务宕机 | 立即回滚 |
| 严重错误 | 回滚 |
| 性能下降超过 50% | 考虑回滚 |
| 细微问题 | 可快速修复则向前修复 |
不同平台的回滚策略
| 平台 | 回滚方式 |
|---|---|
| Vercel/Netlify | 重新部署之前的提交 |
| Railway/Render | 控制面板回滚 |
| VPS + PM2 | 还原备份并重启 |
| Docker | 使用之前的镜像标签 |
| K8s | kubectl rollout undo |
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.
- 3d ago First seen · 242 lines · 36 tokens per session scan A 815ff4e79f5e
deployment-procedures is a skill published in the GitHub repository MisonL/Ling (9 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 1,767 once invoked, about $0.0002 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 skills, from other repositories
cloud-sync
Set up or check claude-mem cloud sync with cmem.ai Pro. Use when the user says "set up cloud sync", "sync my memories", "cmem pro", "cloud backup", "sync status", or wants their memory database backed up or synced to their cmem.ai account.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
yandex-cloud
Read Yandex Cloud through its REST API. Applies to any question about VMs, metrics, logs, audit events, Kubernetes, managed databases, serverless, networking or any other Yandex Cloud resource. Never shell out to the yc CLI — it is not how this agent reaches Yandex Cloud and is usually not installed.
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
scaffold
Generate deployment-ready infrastructure code from an architecture plan, verify it with adversarial self-review, and bridge to validation — all without deploying.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.