deploying-to-production

deploying-to-production is a skill for Claude Code, Codex from ZhanlinCui/Agent-Skills-Hunter. It costs 50 tokens per session (315 once invoked), scanned A, original, MIT.

A deployment workflow for publishing a web project with GitHub, a service for storing code, and Vercel, a service that builds and hosts websites.

In plain words
What is it for?
Use it to prepare a website or app for production, create or reuse its GitHub repository, push the project, deploy it to Vercel, and check the resulting URL.
Why use it?
It checks that the project builds, puts the code in GitHub, publishes it through Vercel, and verifies that the live site works.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to prepare a website or app for production, create or reuse its GitHub repository, push the project, deploy it to Vercel, and check the resulting URL.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zhanlincui/agent-skills-hunter/deploying-to-production
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.

Any agent
npx skills add ZhanlinCui/Agent-Skills-Hunter --skill deploying-to-production
Clone the repo
git clone --depth 1 https://github.com/ZhanlinCui/Agent-Skills-Hunter

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.

agentmods badge for deploying-to-production

README.md
[![agentmods](https://agentmods.dev/badge/skills/zhanlincui/agent-skills-hunter/deploying-to-production/github.svg)](https://agentmods.dev/skills/zhanlincui/agent-skills-hunter/deploying-to-production)
Your own site
<a href="https://agentmods.dev/skills/zhanlincui/agent-skills-hunter/deploying-to-production"><img src="https://agentmods.dev/badge/skills/zhanlincui/agent-skills-hunter/deploying-to-production/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.

agentmods 80×15 button for deploying-to-production

Your own site · 80×15
<a href="https://agentmods.dev/skills/zhanlincui/agent-skills-hunter/deploying-to-production"><img src="https://agentmods.dev/badge/skills/zhanlincui/agent-skills-hunter/deploying-to-production.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00050 $0.00315
Opus 5 $0.00025 $0.00158
Sonnet 5 $0.00010 $0.00063
Haiku 4.5 $0.00005 $0.00032

Measured 12d ago against content hash 2851ddb091e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

deploying-to-production 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 12d 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.

dev/deploying-to-production/SKILL.md · 41 lines

What it actually says

Deploying to Production

Use this workflow when a user says "deploy this website/app" or similar. Follow the checklist in order and do not skip steps.

Deployment Workflow

  • Step 1: Run build and verify no errors
  • Step 2: Create GitHub repository
  • Step 3: Push code to GitHub
  • Step 4: Deploy to Vercel
  • Step 5: Verify deployment

Step 1: Run build

Run:

npm run build

If build fails, read the errors, fix issues, and run again. Only proceed when build succeeds.

Step 2: Create GitHub repository

Create a new GitHub repository for the project. If the repo already exists, confirm whether to reuse or create a new one.

Step 3: Push code to GitHub

Initialize git if needed, add remote, and push the default branch. Confirm the repository contains the expected code.

Step 4: Deploy to Vercel

Deploy the GitHub repo to Vercel. Capture the deployment URL.

Step 5: Verify deployment

Verify the live deployment by opening the URL or checking a response. If verification fails, diagnose and redeploy.

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. 12d ago First seen · 41 lines · 50 tokens per session scan A 2851ddb091e0

Subscribe to this mod's changes

deploying-to-production is a skill published in the GitHub repository ZhanlinCui/Agent-Skills-Hunter (186 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 315 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.