Borrowing it
Nothing to install: this file belongs to MisonL/Ling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MisonL/Ling/main/.agents/skills/deployment-procedures/SKILL.mdgit clone --depth 1 https://github.com/MisonL/LingWrote 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/skills/misonl/ling/deployment-procedures)<a href="https://agentmods.dev/skills/misonl/ling/deployment-procedures"><img src="https://agentmods.dev/badge/skills/misonl/ling/deployment-procedures/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/misonl/ling/deployment-procedures"><img src="https://agentmods.dev/badge/skills/misonl/ling/deployment-procedures.svg" alt="Reviewed on agentmods" width="80" 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.00036 | $0.01767 |
| Opus 5.5 | $0.00014 | $0.00707 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 242 lines · 36 tokens per session scan A 815ff4e79f5e
deployment-procedures is a skill published in the GitHub repository MisonL/Ling (8 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 1,767 once invoked, about $0.0001 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…