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 agentmods add skills/mrhinkle/vibecoding-a-website/deploy-to-vercelnpx skills add mrhinkle/VibeCoding-a-Website --skill deploy-to-vercelgit clone --depth 1 https://github.com/mrhinkle/VibeCoding-a-WebsiteWrote 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/mrhinkle/vibecoding-a-website/deploy-to-vercel)<a href="https://agentmods.dev/skills/mrhinkle/vibecoding-a-website/deploy-to-vercel"><img src="https://agentmods.dev/badge/skills/mrhinkle/vibecoding-a-website/deploy-to-vercel.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 | $0.00000 | $0.02948 |
| Opus 5 | $0.00000 | $0.01474 |
| Sonnet 5 | $0.00000 | $0.00590 |
| Haiku 4.5 | $0.00000 | $0.00295 |
Grade A, and why
deploy-to-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 5d 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Deploy to Vercel
Purpose: Guide users through the complete GitHub → Vercel deployment pipeline to take their website live.
Audience: Business professionals who have built a website using Claude Code + Manus and are ready to deploy.
Use this skill when:
- User is ready to deploy their website for the first time
- User wants to understand the deployment process before going live
- User needs to redeploy after making changes
- User wants to set up a custom domain
- User is troubleshooting deployment issues
Overview
Deploying to Vercel is the final step before your site goes live. This skill walks you through:
- Preparing your code - Initialize git, create proper .gitignore
- Publishing to GitHub - Create a repository and push your code
- Connecting to Vercel - Link GitHub and set up deployment
- Configuring your site - Add environment variables, set up domains
- Pre-launch checklist - Verify everything works before going live
No previous experience with Git or command-line tools required. We'll guide you through each step.
The Deployment Pipeline
Your Local Files
↓
Git Repository
↓
GitHub
↓
Vercel (Auto-deploys)
↓
Live Website
Every time you push changes to GitHub, Vercel automatically rebuilds and redeploys your site. This means updates go live in seconds without any manual steps.
Step 1: Prepare Your Code
What is Git?
Git is a tool that tracks changes to your files. Think of it like version control for documents — you can see what changed, who changed it, and revert to previous versions if needed.
Initialize a Git Repository
Open your terminal in your project directory and run:
git init
This creates a hidden .git folder that tracks all your files.
Create a .gitignore File
Some files shouldn't be uploaded to GitHub (passwords, API keys, node_modules, etc.). Create a .gitignore file in your project root with this content:
# Dependencies
node_modules/
.env
.env.local
.env.*.local
# OS files
.DS_Store
Thumbs.db
# IDE files
.vscode/
.idea/
*.swp
# Build output
dist/
build/
.next/
# Logs
npm-debug.log*
yarn-debug.log*
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.
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.
- 5d ago First seen · 450 lines · 0 tokens per session scan A 14eef8a3a063
deploy-to-vercel is a skill published in the GitHub repository mrhinkle/VibeCoding-a-Website (11 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,948 tokens. 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
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-sbom
Atmos SBOM provenance: CycloneDX and SPDX generation from vendor and Terraform evidence, coverage diagnostics, NTIA validation, and native CI workflow-artifact publication.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
atmos-cache
Atmos caching: CI cache configuration and commands, GitHub Actions cache integration, Terraform registry cache mirror/list/prune/stats/trust, and cache modernization guidance.