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/lukedj78/dev-flow/vercel-deploynpx skills add lukedj78/dev-flow --skill vercel-deploygit clone --depth 1 https://github.com/lukedj78/dev-flowWhat 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.00230 | $0.04347 |
| Opus 5 | $0.00115 | $0.02174 |
| Sonnet 5 | $0.00046 | $0.00869 |
| Haiku 4.5 | $0.00023 | $0.00435 |
Grade A, and why
vercel-deploy 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS -o /dev/null -w '%{http_code}\n' https://<production-domain>/ How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vercel-deploy — ship the web app to production on Vercel
The web counterpart of rn-eas-deploy. It is the only skill that moves a web project to phase = "deployed".
Versions checked 2026-08-04: Vercel CLI
58.5.1. Docs: https://vercel.com/docs/cli/deploy, https://vercel.com/docs/cli/deploying-from-cli, https://vercel.com/docs/cli/promote, https://vercel.com/docs/cli/rollback, https://vercel.com/docs/deployments/promoting-a-deployment, https://vercel.com/docs/instant-rollback, https://vercel.com/docs/git, https://vercel.com/docs/domains/working-with-domains/add-a-domain.
Scope — read this first
This skill ships. It does not configure.
| Concern | Owner |
|---|---|
vercel.json, function region, env-var matrix per environment, monorepo Root Directory, project linking |
module-add deploy — run it first |
| husky, lint-staged, GitHub Actions | module-add ci |
| cost/perf gate before shipping | vercel-doctor |
| legal/privacy gate before shipping | compliance-audit |
| UI-quality / accessibility gate before shipping | shadscan |
preview → smoke → staged production → promote, domains + DNS, rollback, phase = "deployed" |
this skill |
If vercel.json or .vercel/project.json is missing, do not improvise them here — say so and route to module-add deploy. Two skills writing the same config is how the region silently changes between runs.
Contract
See references/contracts.md. Key facts:
- Reads
<project-root>/.workflow/meta.json#stack.framework— must be"next"or"monorepo". - Requires
meta.json#phase >= "feature_complete". - Sets
meta.json#stack.deploy = "vercel"andphase = "deployed"only after the production domain actually serves the deployment. - Records
stack_config.production_url+stack_config.vercel_projectand appendshistory. - Idempotent: re-running on an already-deployed project becomes a release run (deploy → promote), and skips domain setup that is already verified.
What ships with it
4 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.
- 2d ago First seen · 278 lines · 230 tokens per session scan A 307518031a18
vercel-deploy is a skill published in the GitHub repository lukedj78/dev-flow (5 stars, last pushed 4d ago), licensed MIT. It adds 230 tokens to every session and 4,347 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
kirby-performance-and-media
Improves Kirby performance and media delivery (cache tuning, CDN, responsive images, lazy loading). Use when optimizing page speed, caching, or image handling.
prometheus
Prometheus monitoring and alerting for cloud-native observability. Use when implementing metrics collection, PromQL queries, alerting rules, service discovery, recording rules, and scrape config.
resource
SmartCMP resource browsing, detail inspection, recycle-bin management, resource-first Security posture and violation analysis, comprehensive single-resource analysis coordination, and user-scoped operations. Use when the user asks whether a named or selected resource is secure or has Security violations, wants an…
azure-cost-management
Expert knowledge for Azure Cost Management development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, integrations & coding patterns, and deployment. Use when managing budgets/alerts, exports, Cost Management APIs…
aws
Skill "aws" from dhaupin/vant, covering aws, when to use, what to do, 1. services and 2. cli.