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 agentmods add skills/vercel/next.js/deploy-release-testnpx skills add vercel/next.js --skill deploy-release-testgit clone --depth 1 https://github.com/vercel/next.jsWhat 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 | $0.00115 | $0.01173 |
| Opus 5 | $0.00057 | $0.00587 |
| Sonnet 5 | $0.00023 | $0.00235 |
| Haiku 4.5 | $0.00012 | $0.00117 |
Grade A, and why
deploy-release-test 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 2d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Release Test
Use this skill only when manually running the entire Next.js deployment test suite for a pull request. Treat package validation as a hard gate: never dispatch the workflow until the exact commit's redirected tarball responds successfully.
Scope
Do not use this workflow to sanity-check one deployment test or a focused group of tests. Follow Running Deploy Tests Locally instead:
NEXT_TEST_VERSION=https://vercel-packages.vercel.app/next/commits/<commit-sha>/next pnpm test-deploy <path-to-test>
If a request to "run deploy tests" does not explicitly call for the entire suite, prefer the focused local workflow and scope it to the affected tests.
Inputs
- Accept a PR number or determine the PR from the current branch.
- Use repository
vercel/next.jsand workflow.github/workflows/test_e2e_deploy_release.yml. - Require the PR head branch to exist in
vercel/next.js. A fork branch cannot run this secret-bearing workflow; use the repository's PR adoption process first when appropriate.
Workflow
-
Resolve the PR branch and its latest commit from GitHub, not merely from the local checkout:
gh pr view <pr-number> --repo vercel/next.js \ --json number,url,headRefName,headRefOid,isCrossRepositoryIf no PR number was supplied, omit
<pr-number>to detect the PR from the current branch. Stop ifisCrossRepositoryistrue. RecordheadRefNameas the branch andheadRefOidas the commit SHA. -
Construct the exact package URL:
https://vercel-packages.vercel.app/next/commits/<commit-sha>/next -
Wait for the package to become downloadable before dispatching anything:
node scripts/wait-for-preview-tarball.mjs --commit-sha <commit-sha>Keep the wait in an ongoing terminal session and poll it so the user still receives progress updates. The helper uses
HEAD, follows the redirect to Vercel Blob, and only succeeds when the final artifact is available. Do not substitute a check that accepts the initial redirect: that endpoint can redirect even while the blob still returns 404.
What ships with it
1 file 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.
- 2d ago First seen · 130 lines · 115 tokens per session scan A 40eb7dba06ba
deploy-release-test is a skill published in the GitHub repository vercel/next.js (142,020 stars, last pushed 2d ago), licensed MIT. It adds 115 tokens to every session and 1,173 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
triage-ci-flake
Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.
testing-conventions
Use when adding or changing tests, the e2e harness, test process isolation, or CI test sharding.
running-release-tests
Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test profile. Use when the user wants to validate multi-step workflows, verify features, check for regressions, or test API endpoints. Trigger words include run tests, UAT, test my app, test profile, UI test, API test, automated…
local-ci
Run this repository's local CI parity commands and pnpm run ci:local jobs. Use when validating a change against the same job shapes used in GitHub Actions, choosing the smallest local CI job for a package, workflow, E2E, Metro, devtools, bundle-size, or build-and-test change.
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
run-e2e-ci
Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment. Use when asked to "run e2e", "trigger e2e on CI", or "run coin testers" for a PR/branch.