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 skills add itsnex1s/awesome-claude-skills --skill vercel-cligit clone --depth 1 https://github.com/itsnex1s/awesome-claude-skillsWrote 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/itsnex1s/awesome-claude-skills/vercel-cli)<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/vercel-cli"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/vercel-cli/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.
<a href="https://agentmods.dev/skills/itsnex1s/awesome-claude-skills/vercel-cli"><img src="https://agentmods.dev/badge/skills/itsnex1s/awesome-claude-skills/vercel-cli.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.01563 |
| Opus 5 | $0.00014 | $0.00781 |
| Sonnet 5 | $0.00005 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
vercel-cli 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vercel-cli
Deploy, manage environment variables, view logs, configure domains, and set up cron jobs with Vercel CLI.
Installation
npm install -g vercel
vercel login
vercel link
Quick Reference
Project Setup
vercel init # Initialize new project
vercel link # Link existing directory to Vercel project
vercel whoami # Show current user
vercel project ls # List projects
Deployment
vercel # Deploy preview
vercel --prod # Deploy to production
vercel deploy --force # Force redeploy
vercel deploy --env NODE_ENV=production -e API_KEY=secret
# Build locally first
vercel build
vercel deploy --prebuilt
# Manage deployments
vercel redeploy <deployment-url-or-id> # Rebuild + redeploy
vercel promote <deployment-url-or-id> # Promote preview to production
vercel rollback <deployment-url-or-id> # Rollback to previous
# List and inspect
vercel list # List all deployments
vercel inspect <deployment-url-or-id> # Get deployment info
vercel remove <deployment-id> # Delete deployment
Environment Variables
List
vercel env ls # List all env vars
vercel env ls production # List for specific environment
vercel env ls preview
vercel env ls development
Add
vercel env add MY_VAR # Add interactively
vercel env add API_TOKEN production # Add to specific environment
vercel env add SECRET_KEY --sensitive # Add sensitive (masked)
vercel env add MY_VAR --force # Override existing
vercel env add DB_URL production main # Add for specific branch
Update
vercel env update MY_VAR # Update interactively
vercel env update API_TOKEN production # Update specific environment
echo "value" | vercel env update MY_VAR production # From stdin
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.
- 12d ago First seen · 239 lines · 27 tokens per session scan A 9e42f3eb5165
vercel-cli is a skill published in the GitHub repository itsnex1s/awesome-claude-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 1,563 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
awesome-azd-template-submit
Submit an azd template to the awesome-azd gallery. Use when asked to submit, add, or contribute a template to awesome-azd. Requires only a GitHub repository URL — all metadata (title, description, languages, frameworks, Azure services, IaC) is auto-detected by the submission pipeline.
bedrock-agentcore
Deploy and operate agents on Amazon Bedrock AgentCore — Runtime, Harness, Memory, Identity, and Observability. Use when hosting an agent on AWS, containerising an agent for AgentCore Runtime, wiring session or long-term memory, or choosing between Harness, Runtime, and plain Lambda.
mcp-server-hosting
Build and host a remote MCP server on AWS — Lambda, Fargate/ECS, or AgentCore Runtime — with OAuth via Cognito, Okta, or Auth0 and the RFC 7235 401 + WWW-Authenticate handshake. Use when deploying an MCP server for remote agents rather than local stdio use.
expo-eas-build
A guide to profile discipline, credentials management, and the build process for EAS Build. Scoped to eas.json configuration, iOS provisioning + push cert, Android keystore + service account, secrets, and monorepo support. Store-submit DETAIL lives in expo-eas-submit.
expo-eas-update
Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.
expo-dev-client
Custom development builds with expo-dev-client, build profiles, a custom dev menu, runtime-version compatibility, and EAS Update integration. Triggers on expo-dev-client, dev client, custom dev build, development build, dev menu, expo go, runtime version, debug build, dev launcher, scan qr, dev server.