What is deploy-to-vercel?

A deployment workflow for putting applications and websites on Vercel, a hosting platform for web projects. It checks the project’s Git connection, Vercel link, login, and available teams before deploying.

Deploy a project for review, inspect its Vercel setup, link it to a Vercel project, and return a deployment link when available.

It helps avoid deploying to the wrong project or team and provides a route to preview deployments and future Git-based deployments.

deploy-to-vercel — Skill for Claude Code and Codex by CraftOS-dev: A deployment workflow for putting applications and websites on…

Install

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.

agentmods

npx agentmods add skills/craftos-dev/craftbot/deploy-to-vercel

Any agent

npx skills add CraftOS-dev/CraftBot --skill deploy-to-vercel

Clone the repo

git clone --depth 1 https://github.com/CraftOS-dev/CraftBot

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/craftos-dev/craftbot/deploy-to-vercel.svg)](https://agentmods.dev/skills/craftos-dev/craftbot/deploy-to-vercel)

Your own site

<a href="https://agentmods.dev/skills/craftos-dev/craftbot/deploy-to-vercel"><img src="https://agentmods.dev/badge/skills/craftos-dev/craftbot/deploy-to-vercel.svg" alt="Measured on agentmods" height="20"></a>

Per session 47 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,894 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. Scan, not verified.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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	$0.00047	$0.02894
Opus 5	$0.00023	$0.01447
Sonnet 5	$0.00009	$0.00579
Haiku 4.5	$0.00005	$0.00289

Measured 3d ago against content hash cfcc3dd479ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

deploy-to-vercel scanned grade A with 1 finding 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.

The scan reads SKILL.md. This mod also ships 2 executable files (resources/deploy-codex.sh, resources/deploy.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**Do not** curl or fetch the deployed URL to verify it works. Just return the link.

Origin

This is a copy

100% identical to deploy-to-vercel — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

skills/deploy-to-vercel/SKILL.md · 297 lines

How it starts

The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deploy to Vercel

Deploy any project to Vercel. Always deploy as preview (not production) unless the user explicitly asks for production.

The goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state.

Step 1: Gather Project State

Run all four checks before deciding which method to use:

# 1. Check for a git remote
git remote get-url origin 2>/dev/null

# 2. Check if locally linked to a Vercel project (either file means linked)
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null

# 3. Check if the Vercel CLI is installed and authenticated
vercel whoami 2>/dev/null

# 4. List available teams (if authenticated)
vercel teams list --format json 2>/dev/null

Team selection

If the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation.

Pass the team slug via --scope on all subsequent CLI commands (vercel deploy, vercel link, vercel inspect, etc.):

vercel deploy [path] -y --no-wait --scope <team-slug>

If the project is already linked (.vercel/project.json or .vercel/repo.json exists), the orgId in those files determines the team — no need to ask again. If there is only one team (or just a personal account), skip the prompt and use it directly.

About the .vercel/ directory: A linked project has either:

.vercel/project.json — created by vercel link (single project linking). Contains projectId and orgId.
.vercel/repo.json — created by vercel link --repo (repo-based linking). Contains orgId, remoteName, and a projects array mapping directories to Vercel project IDs.

Either file means the project is linked. Check for both.

Do NOT use vercel project inspect, vercel ls, or vercel link to detect state in an unlinked directory — without a .vercel/ config, they will interactively prompt (or with --yes, silently link as a side-effect). Only vercel whoami is safe to run anywhere.

Read the full file on GitHub · 297 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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 · 297 lines · 47 tokens per session scan A cfcc3dd479ab

Subscribe to this mod's changes

deploy-to-vercel is a skill published in the GitHub repository CraftOS-dev/CraftBot (376 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 2,894 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to deploy-to-vercel, differing in 0 lines, and is treated as a copy.

DevOps and cloud agent-architecture ai ai-agents computer-use-agent content-engineering help-wanted

turix-mac

Computer Use Agent (CUA) for macOS automation using TuriX. Use when you need to perform visual tasks on the desktop, such as opening apps, clicking buttons, or navigating UIs that don't have a CLI or API.

TurixAI/TuriX-CUA · 53 tokens

macos-control

Control macOS GUI applications via mouse automation, keyboard input, screenshots, image recognition, and AppleScript execution. Use when you need to interact with macOS app UIs, take screenshots, click buttons, type text, scroll, drag, or locate images on screen.

NakaokaRei/SwiftAutoGUI · 58 tokens

deploy-to-vercel