sandbox-bench SKILL.md skillA
sandbox-bench from vercel/next.js is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vercel/next.js/sandbox-bench@git:20260730.c53c0a5Pins git:20260730.c53c0a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vercel/next.js
- Path
.agents/skills/sandbox-bench/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260730.c53c0a5, committed Jul 30, 2026
- First version recorded
- Jul 25, 2026
- Size
- 16,597 bytes
- Repository stars
- 143,627
- License
- MIT
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app (rps, latency, p95; TTFB, RSS and document/Flight bytes when the Next side captures them) and, for React changes, through the react repo's flight-ssr-bench fixture (Node AND Edge web-streams paths, Fizz and Flight+Fizz). Use whenever the user asks to bench, perf test, or A/B a React PR, a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Sandbox bench: paired A/B perf runs for React and Next.js changes
Measures what a change is actually worth, end to end: two revisions
("arms") built into otherwise-identical Next.js apps, exercised by the
`bench/render-pipeline` harness on Vercel Sandbox VMs, compared with
paired statistics that treat the VM boot as the unit of replication.
All heavy work happens on sandbox VMs; the laptop only orchestrates.
Scripts live in `scripts/` next to this file and run from anywhere.
Arms are git refs, resolved in cached clones of react and next.js;
the Next side defaults to canary. Everything is cached
content-addressed: first use of a new pair builds caches (~45-60 min
extra, once); later runs boot straight into measurement.
## One-time setup
1. `node scripts/config.mjs show` — if it reports NOT CONFIGURED, ask
the user which Vercel **team** and **project** the sandbox VMs
should run under (these are billed resources; never guess, never
default), then `node scripts/config.mjs set team=<slug> project=<name>`.
Config lives in `~/.config/sandbox-bench/config.json` — never commit
team/project names into the repo.
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_d4wp3qgfd4kzj6u2/f21d8fe37f897309a0b0c68bd89cc7700761815be0ea1008b992dd893bd38a80.json
Then /plugin install sandbox-bench@markdownregistry-d4wp3qgfd4kzj6u2 in Claude Code. It installs git:20260730.c53c0a5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vercel/next.js/sandbox-bench@sha256:f21d8fe37f897309The line at the top of this page pins the label git:20260730.c53c0a5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_d4wp3qgfd4kzj6u2)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vercel/next.js/sandbox-bench since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of sandbox-bench from somewhere else? Ask it: where did my sandbox-bench come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 2 versions of this file, between Jul 25, 2026 and Jul 30, 2026, about one every 5 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260730.c53c0a5 latest | 2026-07-30 | c53c0a5 | 16,597 B | A | view · diff |
| git:20260725.1a028f7 | 2026-07-25 | 1a028f7 | 15,474 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/sandbox-bench/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (16597 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
vercel/next.js · 143,627 stars · license MIT · pushed 2026-11-21 · branch canary
API
GET https://markdownregistry.com/api/v1/artifacts/art_d4wp3qgfd4kzj6u2 GET https://markdownregistry.com/api/v1/resolve?ref=vercel/next.js/sandbox-bench GET https://markdownregistry.com/api/v1/blob/f21d8fe37f897309a0b0c68bd89cc7700761815be0ea1008b992dd893bd38a80
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from vercel/next.js
Browse by kind, by grade A, or by owner.
Kept in .agents/skills, the folder Codex reads. More agent skills for Codex.