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/cam-douglas/agent-instructions/vercel-deploy-workflownpx skills add cam-douglas/agent-instructions --skill vercel-deploy-workflowgit clone --depth 1 https://github.com/cam-douglas/agent-instructionsWrote 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/cam-douglas/agent-instructions/vercel-deploy-workflow)<a href="https://agentmods.dev/skills/cam-douglas/agent-instructions/vercel-deploy-workflow"><img src="https://agentmods.dev/badge/skills/cam-douglas/agent-instructions/vercel-deploy-workflow.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.00025 | $0.00585 |
| Opus 5 | $0.00013 | $0.00293 |
| Sonnet 5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00059 |
Grade A, and why
vercel-deploy-workflow 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Vercel — deploy, Git sync, and local/CLI workflow
Purpose
- Ship Next.js changes to Vercel and keep dashboard deployments aligned with repository state; use CLI or Git deliberately.
When to use
- Deploying a Next.js project; verifying why production differs from local; setting up a new clone with Vercel linkage; pulling env for local development.
Inputs
- Repo root path; Git remote with access; Vercel account and team; optional
vercel loginsession.
Tools used
- Git + Vercel Git integration (push → build), or Vercel CLI (
vercel link,vercel,vercel --prod). npm run buildto validate before deploy.npx vercelwhen global CLI is not installed.
Procedure
- Prefer Git workflow when the project is Git-connected: commit and push to the branch Vercel tracks; confirm the new deployment in the Vercel dashboard (commit SHA / branch).
- CLI preview deploy: from repo root,
vercel loginif needed,vercel linkonce, thenvercelfor a Preview deployment of the current tree. - CLI production deploy:
vercel --prodwhen intentionally deploying from CLI (ensure correct branch/commit and team). - Env for local dev:
vercel env pull .env.localafter linking (user verifies secrets); align dashboard env with what the app expects (NEXT_PUBLIC_*only for client-exposed values). - If Vercel MCP is available and authenticated: optional
deploy_to_vercel/ project queries; otherwise use dashboard + CLI.
Expected outcome
- A deployment record in Vercel (Preview or Production) that matches the intended commit or local upload; app URL updated per Vercel’s URL rules.
Validation
- Dashboard shows successful build; preview URL loads; for Git flow, deployment lists the expected commit.
Failure modes / cautions
- Wrong team/project: run
vercel whoamiand re-vercel link. - Uncommitted files: CLI deploy can include working-tree changes — know what you ship.
- MCP without auth: fall back to CLI.
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 · 55 lines · 25 tokens per session scan A 4b0cab0c0e53
vercel-deploy-workflow is a skill published in the GitHub repository cam-douglas/agent-instructions (2 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 585 once invoked, about $0.0001 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-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…