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 skills add xushuodasd/VIBE-Claude-Plugin --skill vibe-deploygit clone --depth 1 https://github.com/xushuodasd/VIBE-Claude-PluginWrote 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/xushuodasd/vibe-claude-plugin/vibe-deploy)<a href="https://agentmods.dev/skills/xushuodasd/vibe-claude-plugin/vibe-deploy"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-deploy/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/xushuodasd/vibe-claude-plugin/vibe-deploy"><img src="https://agentmods.dev/badge/skills/xushuodasd/vibe-claude-plugin/vibe-deploy.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.00015 | $0.01783 |
| Opus 5 | $0.00008 | $0.00892 |
| Sonnet 5 | $0.00003 | $0.00357 |
| Haiku 4.5 | $0.00002 | $0.00178 |
Grade A, and why
vibe-deploy 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 10d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
部署与运维文档制作工作流
1. 基本信息
- 名称：部署与运维文档制作工作流
- 目标：了解和记录现有项目的启动部署流程，包括部署流程、CI/CD、回滚方案、监控告警、日志位置等实际情况
2. 前置步骤
产物检查
-
检查项目结构：
- 确认项目的基本结构和技术栈
- 检查是否存在现有的部署相关配置文件
-
检查依赖项：
- 确认项目的依赖管理方式
- 检查是否有CI/CD配置文件
依赖项确认
-
技术栈确认：
- 确认前端、后端使用的技术栈
- 确认数据库类型和版本
- 确认部署环境要求
-
现有配置检查：
- 检查是否有Dockerfile、docker-compose.yml等容器化配置
- 检查是否有CI/CD配置文件（如.gitlab-ci.yml、Jenkinsfile等）
- 检查是否有环境配置文件
3. 执行步骤
第一步：项目分析与信息收集
-
项目结构分析：
- 分析项目的目录结构
- 识别核心组件和服务
- 了解项目的部署架构
-
技术栈确认：
- 确认前端技术栈（如React、Vue等）
- 确认后端技术栈（如Node.js、Java、Python等）
- 确认数据库类型（如MySQL、MongoDB、Redis等）
- 确认中间件和依赖服务
-
现有配置检查：
- 检查Docker相关配置
- 检查CI/CD配置
- 检查环境变量配置
- 检查网络和端口配置
第二步：部署流程分析
-
环境准备：
- 记录服务器配置要求
- 记录网络环境配置
- 记录依赖安装步骤
-
部署步骤：
- 记录前端部署流程
- 记录后端部署流程
- 记录数据库部署和初始化
- 记录服务启动顺序
-
环境变量配置：
- 记录生产环境配置
- 记录测试环境配置
- 记录开发环境配置
第三步：CI/CD流程分析
-
CI流程：
- 记录代码检查步骤
- 记录构建流程
- 记录测试流程
-
CD流程：
- 记录部署策略
- 记录自动部署触发条件
- 记录部署验证步骤
-
CI/CD配置：
- 记录配置文件内容
- 记录环境变量管理
- 记录构建产物管理
第四步：回滚方案分析
-
回滚策略：
- 记录版本管理策略
- 记录回滚触发条件
- 记录回滚步骤
-
回滚验证：
- 记录回滚后的验证步骤
- 记录服务可用性检查
-
回滚演练：
- 记录定期回滚演练计划
- 记录演练流程
第五步：监控告警分析
-
监控指标：
- 记录系统资源监控（CPU、内存、磁盘、网络）
- 记录应用性能监控
- 记录数据库监控
- 记录服务可用性监控
-
告警机制：
- 记录告警阈值设置
- 记录告警通知渠道
- 记录告警处理流程
-
监控工具：
- 记录监控工具选型
- 记录工具配置
- 记录监控面板设计
第六步：日志管理分析
-
日志位置：
- 记录前端日志位置
- 记录后端日志位置
- 记录数据库日志位置
- 记录系统日志位置
-
日志格式：
- 记录日志格式规范
- 记录日志级别设置
-
日志分析：
- 记录日志收集方案
- 记录日志分析工具
- 记录日志保留策略
第七步：文档编写与整合
-
文档结构：
- 设计部署与运维文档结构
- 章节划分
-
内容编写：
- 按照实际情况编写详细内容
- 确保内容完整覆盖所有要求
- 提供清晰的步骤说明
-
文档审核：
- 内容准确性检查
- 流程完整性检查
- 格式规范检查
4. 执行建议
- 深入了解项目：在编写文档前，充分了解项目的技术栈、架构和现有的部署流程
- 注重细节：详细记录每个步骤和配置，确保文档的准确性
- 保持一致性：确保文档中的术语和流程与项目实际情况一致
- 实际验证：按照记录的步骤进行实际操作验证，确保流程的可操作性
- 定期更新：部署与运维文档应随着项目的发展定期更新
- 提供示例：为关键配置和命令提供示例，方便用户理解
- 与团队沟通：与项目团队保持沟通，确保记录的信息准确无误
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.
- 10d ago First seen · 190 lines · 15 tokens per session scan A 6368ad476ba7
vibe-deploy is a skill published in the GitHub repository xushuodasd/VIBE-Claude-Plugin (4 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 1,783 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 skills, from other repositories
google-agents-cli-deploy
This skill should be used when the user wants to "deploy an agent", "deploy my ADK agent", "set up CI/CD", "configure secrets", "troubleshoot a deployment", or needs guidance on Agent Runtime, Cloud Run, or GKE deployment targets, or binding an agent to an Agent Gateway. Covers deployment workflows, service accounts…
cloud-administration
Administers the cloud the company runs on rather than the one it sells — tenant and subscription structure, the SaaS estate and who owns each app, identity as the real perimeter, cloud spend that arrives as a surprise, and what the provider does not do for you. Use this to structure subscriptions or tenants, get…
telephony-and-conferencing
Runs voice and meeting infrastructure — phone systems and numbers, emergency calling obligations, conference rooms and their AV, call recording and its retention consequences, and the porting that makes provider changes go badly. Use this to replace a phone system, fix rooms nobody can start a meeting in, meet…
business-continuity-and-resilience
Plans for operating through disruption — impact analysis, recovery objectives, continuity plans, and the exercises that prove they work. Use this to run a business impact analysis, set RTO and RPO, write or test a continuity plan, prepare for a supplier or site failure, or answer a customer's resilience questionnaire.
cloud-infrastructure
Designs and runs cloud infrastructure — environments, infrastructure as code, networking and isolation, scaling, and cost. Use this to design a cloud environment, control infrastructure spend, set up environment separation, plan for scale or region failure, or review infrastructure someone configured by hand.
cloudflare
Manage Cloudflare DNS, zones, cache, tunnels, Workers and Pages via the Cloudflare API. Use when the user asks about their domains, DNS records, cache purging, or apps hosted on Cloudflare.