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 kazdenc/builder-skills --skill vercel-deploygit clone --depth 1 https://github.com/kazdenc/builder-skillsWrote 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/kazdenc/builder-skills/vercel-deploy)<a href="https://agentmods.dev/skills/kazdenc/builder-skills/vercel-deploy"><img src="https://agentmods.dev/badge/skills/kazdenc/builder-skills/vercel-deploy.svg" alt="Measured on agentmods" 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.00066 | $0.01996 |
| Opus 5 | $0.00033 | $0.00998 |
| Sonnet 5 | $0.00013 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00200 |
Grade A, and why
vercel-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 7d 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel Deployment
Deploy and configure a project on Vercel. If target specifies a particular concern (domains, env vars, etc.), focus there. Otherwise, do the full setup.
Step 1: Install and Authenticate
pnpm add -g vercel
vercel login
If already installed, verify with vercel --version.
Step 2: Link the Project
From the project root:
vercel link
Follow the prompts to connect to an existing Vercel project or create a new one. This creates a .vercel/ directory locally (already in .gitignore by default).
Step 3: Configure vercel.json
Create vercel.json in the project root only if you need non-default settings. Next.js projects usually need minimal config.
{
"framework": "nextjs",
"buildCommand": "pnpm build",
"installCommand": "pnpm install",
"headers": [
{
"source": "/(.*)",
"headers": [
{ "key": "X-Content-Type-Options", "value": "nosniff" },
{ "key": "X-Frame-Options", "value": "DENY" },
{ "key": "Referrer-Policy", "value": "strict-origin-when-cross-origin" }
]
}
],
"redirects": [],
"rewrites": []
}
| Field | When to set |
|---|---|
framework |
Auto-detected for Next.js. Set explicitly if detection fails. |
buildCommand |
Override if using a monorepo or custom build step |
installCommand |
Override if not using npm (e.g., pnpm install) |
headers |
Add security headers, CORS, caching |
redirects |
Domain migrations, URL restructuring |
rewrites |
Proxy API routes, SPA fallbacks |
regions |
Pin serverless functions to specific regions (e.g., ["iad1"]) |
Step 4: Environment Variables
Set via CLI
# Add for all environments
vercel env add NEXT_PUBLIC_APP_URL
# Add for specific environments
vercel env add DATABASE_URL production
vercel env add DATABASE_URL preview
vercel env add DATABASE_URL development
Environment Types
| Environment | When used | Notes |
|---|---|---|
| Production | Main branch deploys | Use production database, real API keys |
| Preview | PR and branch deploys | Use staging database, test API keys |
| Development | vercel dev locally |
Mirrors .env.local |
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.
- 7d ago First seen · 267 lines · 66 tokens per session scan A 02609e4b232a
vercel-deploy is a skill published in the GitHub repository kazdenc/builder-skills (44 stars, last pushed 6mo ago), licensed MIT. It adds 66 tokens to every session and 1,996 once invoked, about $0.0003 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-30.
Other skills, from other repositories
adapter-aws-lambda
Deploy tRPC on AWS Lambda with awsLambdaRequestHandler() from @trpc/server/adapters/aws-lambda for API Gateway v1 (REST, APIGatewayProxyEvent) and v2 (HTTP, APIGatewayProxyEventV2), and Lambda Function URLs. Enable response streaming with awsLambdaStreamingRequestHandler() wrapped in awslambda.streamifyResponse().…
adapter-fetch
Deploy tRPC on WinterCG-compliant edge runtimes with fetchRequestHandler() from @trpc/server/adapters/fetch. Supports Cloudflare Workers, Deno Deploy, Vercel Edge Runtime, Astro, Remix, SolidStart. FetchCreateContextFnOptions provides req (Request) and resHeaders (Headers) for context creation. The endpoint option…
trigger-cost-savings
Analyze Trigger.dev tasks, schedules, and runs for cost optimization opportunities. Use when asked to reduce spend, optimize costs, audit usage, right-size machines, or review task efficiency. Combines static source analysis with live run analysis via the Trigger.dev MCP tools (listruns, getrundetails…
portaljs-deploy
Deploy a PortalJS portal to PortalJS Arc — Datopian-managed static hosting on Cloudflare. Builds a static export, uploads it, and returns a live SLUG.arc.portaljs.com URL. One command, one target. Use when a portal is ready to publish or redeploy to a live URL.
prepare-cloudflare-production-deployment
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment. Use when setting up or auditing Cloudflare MCP resources, wrangler.jsonc bindings, Worker secrets, Turnstile, Email Sending, GitHub Actions secrets/variables, or GitHub CLI deployment wiring for this…
deploy-release
Prepare and verify a staged or production deployment with rollback and smoke checks.