jev-vercel-sandbox

jev-vercel-sandbox is a plugin for Claude Code from davila7/claude-code-templates. Its token cost is not measured, scanned A, original, MIT.

A command runner that sends risky Bash commands to an isolated Linux microVM in Vercel Sandbox instead of running them directly on your computer. A classifier decides when a command crosses the configured risk threshold.

In plain words
What is it for?
Use it to run dangerous shell commands in an isolated environment and inspect the results from the session's side panel.
Why use it?
It limits the impact of destructive commands, remote code, machine changes, or data leaving the system. The command output is returned to the coding session with information about where it ran.

Plugin for Claude Code

Written for Claude Code: a Claude Code plugin manifest.

Good fit Use it to run dangerous shell commands in an isolated environment and inspect the results from the session's side panel.

Compare 6 plugins from other repositories ↓
Install in Claude Code
/plugin marketplace add davila7/claude-code-templates
/plugin install jev-vercel-sandbox
About the project

Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.

davila7/claude-code-templates · 33,152 stars · on GitHub · aitmpl.com

Install

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.

Clone the repo
git clone --depth 1 https://github.com/davila7/claude-code-templates

Made for: Claude Code.

Wrote 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.

agentmods badge for jev-vercel-sandbox

README.md
[![agentmods](https://agentmods.dev/badge/plugins/davila7/claude-code-templates/jev-vercel-sandbox/github.svg)](https://agentmods.dev/plugins/davila7/claude-code-templates/jev-vercel-sandbox)
Your own site
<a href="https://agentmods.dev/plugins/davila7/claude-code-templates/jev-vercel-sandbox"><img src="https://agentmods.dev/badge/plugins/davila7/claude-code-templates/jev-vercel-sandbox/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.

agentmods 80×15 button for jev-vercel-sandbox

Your own site · 80×15
<a href="https://agentmods.dev/plugins/davila7/claude-code-templates/jev-vercel-sandbox"><img src="https://agentmods.dev/badge/plugins/davila7/claude-code-templates/jev-vercel-sandbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

jev-vercel-sandbox 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 1mo 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.

cli-tool/components/mods/security/jev-vercel-sandbox/.claude-plugin/plugin.json · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.

{
  "name": "jev-vercel-sandbox",
  "version": "0.3.0",
  "description": "A Vercel Sandbox Claude sends work to on purpose: long test runs in the background, someone else's repository, an installer of unknown origin, a bulk change to preview as a patch, a clean build. TypeSafe's Jev reads each Bash command and spots those jobs; by default you are asked whether it runs in the sandbox or locally (confirmSandbox), or it always goes to the sandbox with the question off. Claude also gets sandbox_run, sandbox_jobs, sandbox_result and sandbox_apply. Each job starts from the project as it is now (tracked files, credentials left out) in its own worktree, every result is marked remote, and a job's changes reach your disk only as a patch you apply after a question. /jev-vercel-sandbox starts it and opens a side pane with the jobs. Falls back to the engine's built-in classifier without a Jev key.",
  "author": {
    "name": "claude-code-templates",
    "url": "https://www.aitmpl.com"
  },
  "repository": "https://github.com/davila7/claude-code-templates",
  "license": "MIT",
  "keywords": [
    "mod",
    "function-hooks",
    "security",
    "sandbox",
    "vercel",
    "jev",
    "typesafe",
    "bash",
    "tests"
  ],
  "userConfig": {
    "vercelToken": {
      "type": "string",
      "title": "Vercel token",
      "description": "A Vercel access token (vercel.com/account/tokens), or an OIDC token from `vercel env pull`. Empty: the VERCEL_TOKEN, then VERCEL_OIDC_TOKEN environment variable",
      "sensitive": true,
      "default": ""
    },
    "vercelTeamId": {
      "type": "string",
      "title": "Vercel team id",
      "description": "The team (team_…) the sandbox is billed to; needed with an access token, read from an OIDC token. Empty: VERCEL_TEAM_ID",
      "default": ""
    },
    "vercelProjectId": {
      "type": "string",
      "title": "Vercel project id",
      "description": "The project (prj_…) the sandbox belongs to; needed with an access token, read from

Read the full file on GitHub · 189 lines

Changes

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.

  1. 1mo ago Changed 486f46a260b7
  2. 1mo ago Changed · +6 lines c839b2bd7b96
  3. 1mo ago First seen · 183 lines scan A 08583dbdeb41

Subscribe to this mod's changes

jev-vercel-sandbox is a plugin published in the GitHub repository davila7/claude-code-templates (33,152 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-27.

Related

jev-vercel-sandbox compared with plugins from other repositories

jev-vercel-sandbox next to 6 plugins from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
jev-vercel-sandboxdavila7/claude-code-templatesPlugin33kyesterdayMITA—Claude Code
database-cloud-optimizationwshobson/agentsPlugin42kyesterdayMITA—Claude Code
deployment-strategieswshobson/agentsPlugin42kyesterdayMITA—Claude Code
local-ainaveedharri/benai-skillsPlugin7828d agoMITA—Claude Code
product-managementandisab/swe-marketplacePlugin21yesterdayMITA—Claude Code
commander-hub marketplaceKevinZai/commanderPlugin6yesterdayMITA—Claude Code
bleuNirvaan05/Bleu-PluginPlugin44mo agoMITA—Claude Code