deploy

A release guide for publishing completed non-developer MVPs on Vercel, a service that hosts web applications online.

In plain words
What is it for?
It helps deploy a finished Next.js app through the Vercel command line or a GitHub connection, with HTTPS and a custom domain.
Why use it?
It provides checks for missing environment settings, failed builds, and leftover local URLs before the app is published.

Command for Claude Code

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 commands/ccivlcid/vibeharness/deploy
Clone the repo
git clone --depth 1 https://github.com/ccivlcid/VibeHarness

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 510 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00510
Opus 5 $0.00000 $0.00255
Sonnet 5 $0.00000 $0.00102
Haiku 4.5 $0.00000 $0.00051

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

Security

Grade A, and why

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 3d 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.

.claude/commands/deploy.md · 73 lines

How it starts

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

Deploy — Free Vercel Deployment

This command is part of the VibeHarness framework. Use this command only after development is complete. Never mention deployment during development. Update PROJECT_RULES.md deployment field after deploying. Update Progress.md status. When all P0 features are done and tested, guide the user: "Everything is ready! Want to put it on the internet so others can see it?"

Deploy non-developer MVPs to the internet for free.

Why Vercel

  • Made by the creators of Next.js — easiest Next.js deployment
  • Connect GitHub for automatic deploys on every push
  • Free tier: custom domain, HTTPS, global CDN included
  • Almost zero configuration — non-developers can handle it

Pre-Deploy Checklist

  1. Environment variables: Values in .env.local need to be added to Vercel dashboard
  2. Build test: npm run build must pass without errors
  3. Remove hardcoded URLs: No localhost:3000 left in code

Deployment Methods

Method 1: Vercel CLI (recommended)

npm i -g vercel
vercel login
vercel

Answer the prompts on first deploy — auto-configured.

Method 2: GitHub Integration

  1. Push code to GitHub
  2. Connect GitHub on vercel.com
  3. Select repository — auto-deploy

Environment Variables

Vercel Dashboard → Settings → Environment Variables:

DATABASE_URL=file:./dev.db
NEXTAUTH_SECRET=your-secret-key

Note: Variables with NEXT_PUBLIC_ prefix are exposed to the browser. Keep secret keys without the prefix.

Post-Deploy Verification

  • Visit the deploy URL (xxx.vercel.app) and verify it works
  • Test on mobile too (responsive check)
  • Test key features (login, signup, etc.)

Guiding Non-Developers

After deployment is complete:

  • "You can see your app here: https://xxx.vercel.app"
  • "It works on your phone too — same address"
  • "When I update the code, it automatically updates"

Custom Domain

If the non-developer wants to connect their own domain:

  1. Vercel Dashboard → Settings → Domains
  2. Add domain
  3. Guide DNS setup step by step

Read the full file on GitHub · 73 lines

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.

  1. 3d ago First seen · 73 lines · 0 tokens per session scan A 71003c381c3c

Subscribe to this mod's changes

deploy is a command published in the GitHub repository ccivlcid/VibeHarness (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 510 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-31.