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 FortiumPartners/ensemble --skill managing-vercelgit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/managing-vercel)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/managing-vercel"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/managing-vercel.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.00038 | $0.02689 |
| Opus 5 | $0.00019 | $0.01345 |
| Sonnet 5 | $0.00008 | $0.00538 |
| Haiku 4.5 | $0.00004 | $0.00269 |
Grade A, and why
managing-vercel 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 4d 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vercel CLI Skill
Purpose: Fast reference for Vercel CLI operations | Target: <500 lines
Overview
What is Vercel: Frontend cloud platform with automatic CI/CD, serverless functions, edge network, and global CDN. Optimized for Next.js, React, Vue, and other frameworks.
When to Use:
- Deploying frontend applications
- Managing serverless functions and domains
- Managing environment variables
- Debugging deployments and logs
Auto-Detection Triggers:
vercel.jsonin project root.verceldirectory presentVERCEL_TOKENin.envfile
Progressive Disclosure:
- This file: Quick reference for immediate use
- REFERENCE.md: Advanced patterns, CI/CD, troubleshooting deep-dives
Table of Contents
- Critical: Avoiding Interactive Mode
- Prerequisites
- Authentication
- CLI Decision Tree
- Command Reference
- Static Reference Data
- Common Workflows
- Error Handling
- Framework Examples
- Agent Integration
- Quick Reference Card
Critical: Avoiding Interactive Mode
Vercel CLI can hang Claude Code. Always use flags to bypass prompts:
| Command | WRONG | CORRECT |
|---|---|---|
| Deploy | vercel |
vercel --yes --token $VERCEL_TOKEN |
| Link | vercel link |
vercel link --yes --project <name> |
| Pull env | vercel pull |
vercel pull --yes --environment production |
| Add env | vercel env add |
vercel env add NAME production < value.txt |
| Remove | vercel env rm NAME |
vercel env rm NAME --yes |
Required flags: --yes, --token <TOKEN>, explicit names, --no-wait
Never use: vercel login, vercel dev, commands without --yes when modifying
Prerequisites
# Check CLI
vercel --version # Expects: 30.x.x+
# Install
npm i -g vercel
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.
- 4d ago First seen · 378 lines · 38 tokens per session scan A 13888560d221
managing-vercel is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 2,689 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
cli-ux
Use for packages/cli changes that affect command UX, prompts, help, output layout, progress, success, warnings, errors, JSON/stdout/stderr contracts, non-interactive/agent behavior, copy, or tests for those surfaces. Do not load for implementation-only refactors with unchanged CLI surface.
x-last
Enhanced last command with CSV, JSON, tree view, and interactive UI for viewing login history. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
x-lsof
Enhanced lsof (List Open Files) with interactive UI and structured output. View open files, network connections, and processes. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
x-ps
Enhanced ps process viewer with interactive UI, fzf support, AI filtering, and CSV/JSON/TSV output formats. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill for installation options). see x-cmd skill for installation.
vs-project
Create Viking web projects, start and verify a local preview, or deploy a generated project to Volcengine IGA Pages when explicitly requested. Includes agent-guided feature, eligible application, dataset, scene, and authentication choices. Use only after confirming the installed CLI exposes vs project; otherwise stop…
netlify
Use when deploying or operating a site on Netlify — writing or fixing netlify.toml, authoring Functions or Edge Functions, redirects, rewrites and headers, env vars per deploy context, and shipping via the Netlify CLI. NOT deploying to Vercel (that is vercel).