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 echoVic/boss-skill --skill deploy-vercelgit clone --depth 1 https://github.com/echoVic/boss-skillWrote 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/echovic/boss-skill/deploy-vercel)<a href="https://agentmods.dev/skills/echovic/boss-skill/deploy-vercel"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/deploy-vercel/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/echovic/boss-skill/deploy-vercel"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/deploy-vercel.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.00041 | $0.01111 |
| Opus 5.5 | $0.00016 | $0.00444 |
| Sonnet 5.5 | $0.00008 | $0.00222 |
| Haiku 4.5 | $0.00004 | $0.00111 |
Grade A, and why
devops/deploy-vercel 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 today.
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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel 部署
适用场景
- Next.js / React / Vue / Svelte 等前端框架
- 静态站点(HTML/CSS/JS)
- Serverless Functions(API Routes)
- 全栈应用(Next.js full-stack)
前置条件
- 安装 Vercel CLI:
npm i -g vercel - 登录 Vercel:
vercel login(需要用户交互完成登录) - 项目根目录有
package.json
部署流程
1. 检测 Vercel 配置
# 检查是否已有 vercel.json
ls vercel.json 2>/dev/null && echo "exists" || echo "missing"
2. 创建 vercel.json(如不存在)
{
"framework": "nextjs",
"buildCommand": "npm run build",
"outputDirectory": ".next",
"installCommand": "npm install",
"devCommand": "npm run dev",
"regions": ["iad1"],
"env": {
"NODE_ENV": "production"
}
}
框架自动检测:Vercel 会自动识别框架,通常无需手动配置 framework。
3. 首次部署
# 首次部署(交互式,需要用户确认项目设置)
vercel
# 非交互式部署(CI 环境)
vercel --yes --prod
首次部署输出示例:
Vercel CLI 37.0.0
🔗 Linked to username/project (created .vercel)
🔍 Inspect: https://vercel.com/username/project/xxx
✅ Production: https://project-xxx.vercel.app
4. 后续部署
# 预览部署(staging)
vercel
# 生产部署
vercel --prod
5. 环境变量管理
# 添加环境变量
vercel env add DATABASE_URL production
# 列出环境变量
vercel env ls
# 删除环境变量
vercel env rm DATABASE_URL production
# 拉取环境变量到本地 .env
vercel env pull .env.local
6. 域名绑定
# 添加自定义域名
vercel domains add example.com
# 列出域名
vercel domains ls
CI/CD 集成
GitHub Actions 自动部署
name: Deploy to Vercel
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: 20
- run: npm ci
- run: npm test
- name: Deploy to Vercel
uses: amondnet/vercel-action@v25
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.ORG_ID }}
vercel-project-id: ${{ secrets.PROJECT_ID }}
vercel-args: "--prod"
需要的 Secrets:
VERCEL_TOKEN:Vercel Personal Access Token(Settings → Tokens)ORG_ID:Vercel 团队/个人 IDPROJECT_ID:Vercel 项目 ID
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.
- today First seen · 170 lines · 41 tokens per session scan A 3e2aa41eae86
devops/deploy-vercel is a skill published in the GitHub repository echoVic/boss-skill (544 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 1,111 once invoked, about $0.0002 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-10-28.
Other skills, from other repositories
linkerd-patterns
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
cost-optimization
Optimize cloud costs across AWS, Azure, GCP, and OCI through resource rightsizing, tagging strategies, reserved instances, and spending analysis. Use when reducing cloud expenses, analyzing infrastructure costs, or implementing cost governance policies.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
convex-ship
Publish the current Convex app to a live .convex.app URL (deploy backend + upload web build).
dokploy-deploy
This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".
openship-config
This skill should be used when the user asks to "create openship.json", "configure an OpenShip deployment", "make a repo deployable on OpenShip", or fix "openship config validate" errors.