next-evals-oss: Skill for Claude Code

.agents/skills/add-eval-model/SKILL.md

add-eval-model is a skill for Claude Code, Codex from vercel/next-evals-oss. It costs 91 tokens per session (3,248 once invoked), scanned A, original, MIT.

A workflow for adding a model to the nextjs.org/evals public evaluation board from setup through published results. It registers the experiment, runs the evaluation matrix, exports the results, and prepares a pull request.

In plain words
What is it for?
Use it to verify a model identifier and evaluation setting, run its comparisons, export the numbers, assign a tier, and open the results pull request.
Why use it?
It avoids treating a model as added when only its configuration exists and no measured results are available on the board.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is vercel/next-evals-oss's own configuration. It tells Claude Code and Codex how to work on next-evals-oss itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything next-evals-oss configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is pnpm typecheck && pnpm test:cost && node scripts/check-stale.mjs.

About the project

vercel/next-evals-oss is a set of evaluations that tests how well AI coding agents complete tasks in Next.js applications. Each evaluation gives an agent a small app in an isolated sandbox and checks the resulting code with assertions that are hidden from the agent. The catalogue entries provide instructions and a skill for running or developing these evaluations.

vercel/next-evals-oss · 315 stars · on GitHub · nextjs.org

Reuse

Borrowing it

Nothing to install: this file belongs to vercel/next-evals-oss. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vercel/next-evals-oss/main/.agents/skills/add-eval-model/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/vercel/next-evals-oss

Made for: Claude Code, Codex.

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 add-eval-model

README.md
[![agentmods](https://agentmods.dev/badge/skills/vercel/next-evals-oss/add-eval-model/github.svg)](https://agentmods.dev/skills/vercel/next-evals-oss/add-eval-model)
Your own site
<a href="https://agentmods.dev/skills/vercel/next-evals-oss/add-eval-model"><img src="https://agentmods.dev/badge/skills/vercel/next-evals-oss/add-eval-model/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 add-eval-model

Your own site · 80×15
<a href="https://agentmods.dev/skills/vercel/next-evals-oss/add-eval-model"><img src="https://agentmods.dev/badge/skills/vercel/next-evals-oss/add-eval-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,248 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.03248
Opus 5 $0.00046 $0.01624
Sonnet 5 $0.00018 $0.00650
Haiku 4.5 $0.00009 $0.00325

Measured yesterday against content hash 85d73c1c8354, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-13, from the pricing page.

Security

Grade A, and why

add-eval-model scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -o /dev/null -w '%{http_code}\n' https://ai-gateway.vercel.sh/v1/messages \
.agents/skills/add-eval-model/SKILL.md · 230 lines

How it starts

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

Adding a model to nextjs.org/evals

The deliverable is a landed run, not a config

A model addition is done when the run has happened, agent-results.json contains its numbers, and a PR against the site repo carries that file. It is not done when the experiment config exists.

export-results only exports experiments that have results, so a registered-but-unrun model does not reach the board at all — the PR looks complete and changes nothing a reader can see. The README's retention policy names this state and rejects it: "a staging post, not a destination — land the run and tier the model in the same PR, or drop the config."

So do not stop after step 2 below and hand back a "ready to run, just needs the go-ahead" PR. The run costs real money (roughly $50–250 for a Fable/Opus-tier pair at list) and takes 30–90 minutes of wall clock. Spend it, then report what it cost. Stop early only when a step is genuinely blocked — pnpm preflight says a credential is missing, or the gateway refuses the model id.

Steps

1. Set up and verify credentials

pnpm install --frozen-lockfile
pnpm sync-evals 071a2343c509751585cd9f77ae66e8c30daf2ea8   # the SHA .github/workflows/eval-cache-check.yml pins
pnpm preflight

Sandbox auth needs either VERCEL_OIDC_TOKEN or all three of VERCEL_TOKEN + VERCEL_TEAM_ID + VERCEL_PROJECT_ID. One or two of the triple is worse than none — it silently falls back to OIDC and dies on Could not get credentials from OIDC context. In a Vercel Devbox the token is usually in the environment and the two IDs are in the injected instructions; put the missing ones in .env.local (gitignored).

Do not proceed on a red preflight.

2. Register the experiment pair

Confirm the model id and the effort rung against the live gateway before writing either into a config. Catalogs disagree with the API and with each other; the gateway is the source of truth.

# Id: an id the gateway does not serve answers 404 model_not_found, so a 200 here is
# real resolution rather than a silent fallback to some default model.
curl -s -o /dev/null -w '%{http_code}\n' https://ai-gateway.vercel.sh/v1/messages \
  -H "Authorization: Bearer $AI_GATEWAY_API_KEY" -H 'Content-Type: application/json' \
  -H 'anthropic-version: 2023-06-01' \
  -d '{"model":"<id>","max_tokens":16,"messages":[{"role":"user","content":"ok"}]}'

# Effort: a bad rung returns 400 enumerating the real set. Worth more than any catalog.
curl -s https://ai-gateway.vercel.sh/v1/chat/completions \
  -H "Authorization: Bearer $AI_GATEWAY_API_KEY" -H 'Content-Type: application/json' \
  -d '{"model":"<provider/id>","reasoning_effort":"<rung>",
       "messages":[{"role":"user","content":"ok"}],"max_tokens":2000}'

Read the full file on GitHub · 230 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. yesterday Changed · +45 lines 85d73c1c8354
  2. 2d ago First seen · 185 lines · 91 tokens per session scan A a0d4b667fc3c

Subscribe to this mod's changes

add-eval-model is a skill published in the GitHub repository vercel/next-evals-oss (315 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 3,248 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens