Protected Vercel Deployments
vercel-labs/agent-browser
Opens Vercel deployments behind Deployment Protection in agent-browser, using a short-lived OIDC token instead of a static bypass secret or a public exception.
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
Install Access Protected Vercel Deployment
$ npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel/vercel-plugin access-protected-vercel-deployment --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/access-protected-vercel-deployment .claude/skills/access-protected-vercel-deployment && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "access-protected-vercel-deployment" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deployment into .claude/skills/access-protected-vercel-deployment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "access-protected-vercel-deployment", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deploymentType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel/vercel-plugin access-protected-vercel-deployment --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/access-protected-vercel-deployment .agents/skills/access-protected-vercel-deployment && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "access-protected-vercel-deployment" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deployment into .agents/skills/access-protected-vercel-deployment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "access-protected-vercel-deployment", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel/vercel-plugin access-protected-vercel-deployment --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/access-protected-vercel-deployment .cursor/skills/access-protected-vercel-deployment && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "access-protected-vercel-deployment" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deployment into .cursor/skills/access-protected-vercel-deployment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "access-protected-vercel-deployment", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel/vercel-plugin.git --path skills/access-protected-vercel-deployment--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel/vercel-plugin access-protected-vercel-deployment --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/access-protected-vercel-deployment .gemini/skills/access-protected-vercel-deployment && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "access-protected-vercel-deployment" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deployment into .gemini/skills/access-protected-vercel-deployment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "access-protected-vercel-deployment", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel/vercel-plugin access-protected-vercel-deploymentInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/access-protected-vercel-deployment .github/skills/access-protected-vercel-deployment && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "access-protected-vercel-deployment" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deployment into .github/skills/access-protected-vercel-deployment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "access-protected-vercel-deployment", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel/vercel-plugin access-protected-vercel-deployment --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel/vercel-plugin.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/access-protected-vercel-deployment .opencode/skills/access-protected-vercel-deployment && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "access-protected-vercel-deployment" agent skill from https://github.com/vercel/vercel-plugin/tree/main/skills/access-protected-vercel-deployment into .opencode/skills/access-protected-vercel-deployment/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "access-protected-vercel-deployment", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
access-protected-vercel-deployment- GitHub stars
- 301
- Token cost
- ~1.9k tokens
- SKILL.md length
- 577 words
- Files
- 2
- Skills in repo
- 38
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
- Another automated request reaches a Vercel login
- SKILL.md covers Choose the access path, Trusted Sources rules, Diagnose the response and Avoid, plus 1 more section
- Calls vercel and sh; needs VERCEL_OIDC_TOKEN
- Protection page
What it does
Access Protected Vercel Deployment is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Use when curl, agent-browser, Playwright, or another automated request reaches a Vercel login or protection page; when a protected preview or production URL returns 401 or 403; when TRUSTEDSOURCESENVIRONMENTMISMATCH appears; or when choosing between vercel curl and the x-vercel-trusted-oidc-idp-token header.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
It sits in DevOps & Cloud, covering Deployment, Authentication and OAuth and OpenID Connect. It works with Vercel and Playwright. The repository describes itself as: Comprehensive Vercel ecosystem plugin — relational knowledge graph, skills for every major product, specialized agents, and Vercel conventions. Turns any AI agent into a Vercel…
When your agent uses it
- Another automated request reaches a Vercel login
- Protection page
- A protected preview
- Production URL returns 401
Example prompts
- “/access-protected-vercel-deployment”
Requirements
- A credential in VERCEL_OIDC_TOKEN
What it can do on your machine
Read from SKILL.md and the folder at commit 82fa491. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
vercelsh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use vercel, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
VERCEL_OIDC_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Access Protected Vercel Deployment loads about 1.9k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 577 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:128
vc env pull .env.local --yes - NoteMentions a .env fileSKILL.md:131
e its value into source code, or commit `.env.local`.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 577 words (~1,906 tokens).
“Use the caller's existing Vercel authentication. Do not disable Deployment Protection or ask for a long-lived bypass secret as the first solution.”
- name
- access-protected-vercel-deployment
- summary
- Access protected Vercel URLs with vercel curl or a short-lived OIDC token
- metadata.priority
- 8
- metadata.docs
- https://vercel.com/docs/cli/curl, https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/trusted-sources…
- metadata.sitemap
- https://vercel.com/sitemap.xml
- metadata.bashPatterns
- \b(?:vercel|vc)\s+curl\b, \b(?:curl|wget)\b[^\n]*\.vercel\.app\b, \bagent-browser\b[^\n]*(?:open|navigate|goto)[^\n]*\.vercel\.app\b…
- retrieval.aliases
- protected Vercel deployment, Vercel SSO bypass, Vercel deployment authentication, Vercel Trusted Sources
- retrieval.intents
- access a protected deployment, test a protected preview, verify a protected production deployment, authenticate browser automation to Vercel
- retrieval.entities
- vercel curl, VERCEL_OIDC_TOKEN, x-vercel-trusted-oidc-idp-token, Trusted Sources, Deployment Protection
- retrieval.examples
- preview is behind Vercel SSO, curl this protected Vercel deployment, access a protected Vercel deployment through a custom domain, open the protected…
Files
SKILL.md and 1 other file in skills/access-protected-vercel-deployment of vercel/vercel-plugin.
- SKILL.md
- .vercel.approvers
Open the folder on GitHubat commit 82fa491
Compare with similar skills
Access Protected Vercel Deployment next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Access Protected Vercel Deployment this skillvercel/vercel-plugin | 301 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Protected Vercel Deploymentsvercel-labs/agent-browser | 44k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Deployambient-code/platform | 131 | — | ~2.6k | Automated safety check: Pass | MIT | |
| Agenttinyfish-io/tinyfish-cookbook | 2.2k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Microsoft Store Publishergithub/awesome-copilot | 40k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Playwright Skilllackeyjb/playwright-skill | 3.2k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
- Official
Deploy
ambient-code/platform
Deploy, update manifests, and troubleshoot the ambient-ui component.
Agent
tinyfish-io/tinyfish-cookbook
Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in…
- Official
Microsoft Store Publisher
github/awesome-copilot
Takes a Windows desktop app through MSIX packaging, WACK validation and a Partner Center submission with the Microsoft Store, with strict confirmation safeguards for risky steps.
Playwright Skill
lackeyjb/playwright-skill
Complete browser automation with Playwright. An agent skill from lackeyjb/playwright-skill.
Frontmcp Config
agentfront/frontmcp
A skill your agent uses when configuring a FrontMCP server through frontmcp.config or the @FrontMcp options.
More from vercel/vercel-plugin
All 38 skills in this repo- Official
Deployments Cicd
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
- Official
Plugin Audit
vercel/vercel-plugin
Audit vercel-plugin performance on real-world projects. An agent skill from vercel/vercel-plugin.
- Official
Vercel CLI
vercel/vercel-plugin
Vercel CLI expert guidance. An agent skill from vercel/vercel-plugin.
- Official
AI Gateway
vercel/vercel-plugin
Vercel AI Gateway guidance for setup, model discovery, authentication, routing, fallbacks, virtual models, evaluation models, BYOK, budgets, spend reporting, observability, compatible APIs, and…
- Official
Vercel Services
vercel/vercel-plugin
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project.
- Official
Bootstrap
vercel/vercel-plugin
Project bootstrapping orchestrator for repos that depend on Vercel-linked resources (databases, auth, and managed integrations).
Related
Works with
Questions about Access Protected Vercel Deployment
What does Access Protected Vercel Deployment do?
Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection. Access Protected Vercel Deployment is an agent skill from vercel/vercel-plugin, published by the product's own GitHub organization. Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection.
When should I use Access Protected Vercel Deployment?
Access Protected Vercel Deployment fits situations like: another automated request reaches a Vercel login; protection page; A protected preview; production URL returns 401.
How do I install Access Protected Vercel Deployment in Claude Code?
Run `npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a claude-code`. Or copy the skill folder (skills/access-protected-vercel-deployment in vercel/vercel-plugin) into .claude/skills/access-protected-vercel-deployment in your project. Claude Code loads it when a task matches its description.
How do I install Access Protected Vercel Deployment in Codex?
Run `npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a codex`. Or copy the skill folder (skills/access-protected-vercel-deployment in vercel/vercel-plugin) into .agents/skills/access-protected-vercel-deployment in your project. Codex loads it when a task matches its description.
Can I use Access Protected Vercel Deployment in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel/vercel-plugin --skill access-protected-vercel-deployment -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/access-protected-vercel-deployment, .gemini/skills/access-protected-vercel-deployment, .github/skills/access-protected-vercel-deployment and .opencode/skills/access-protected-vercel-deployment in your project.
What does Access Protected Vercel Deployment need to run?
Going by SKILL.md and its folder, Access Protected Vercel Deployment needs the command-line tools its instructions call (vercel and sh) and credentials named VERCEL_OIDC_TOKEN. Our summary lists: A credential in VERCEL_OIDC_TOKEN.
Does Access Protected Vercel Deployment access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Access Protected Vercel Deployment safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Access Protected Vercel Deployment use?
Access Protected Vercel Deployment has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Access Protected Vercel Deployment use?
About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Access Protected Vercel Deployment?
Skills that share tags, products or a category with Access Protected Vercel Deployment: Protected Vercel Deployments (vercel-labs/agent-browser, 44k stars), Deploy (ambient-code/platform, 131 stars), Agent (tinyfish-io/tinyfish-cookbook, 2.2k stars) and Microsoft Store Publisher (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Access Protected Vercel Deployment?
vercel (a GitHub organization, an official publisher) maintains it in vercel/vercel-plugin, which has 301 GitHub stars. The repository holds 38 skills in this directory. The repository was last updated on October 6, 2026.
Source: vercel/vercel-plugin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.