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 skills add Phaedra-Solutions/cursor-rules --skill upgrade-nextjsgit clone --depth 1 https://github.com/Phaedra-Solutions/cursor-rulesWrote 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.
[](https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-nextjs)<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-nextjs"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-nextjs/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.
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-nextjs"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-nextjs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00106 | $0.02943 |
| Opus 5.5 | $0.00042 | $0.01177 |
| Sonnet 5.5 | $0.00021 | $0.00589 |
| Haiku 4.5 | $0.00011 | $0.00294 |
Grade A, and why
upgrade-nextjs 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Next.js
When to use
- The user asks to upgrade Next.js, or to move off an unsupported or vulnerable version.
- The installed
nextis below theapplies_torange offrontend/nextjs(16.x) and the user agrees to upgrade. - A security fix exists only in a newer major (14.x gets no fixes; 15.x gets them only through 31 Jan 2027).
For a patch or minor upgrade within the same major, skip to step 3 with upgrade patch or upgrade minor. For moving pages/ to app/, see the migration path in legacy/nextjs-pages-router; don't combine it with a major upgrade.
Before you start
-
Read exact versions from the lockfile:
next,react,react-dom,@types/react,@types/react-dom,eslint-config-next,typescript, and the Node version (.nvmrc,engines, Dockerfile, CI). -
The working tree must be clean. Ask the user to commit or stash first; work on a new branch (for example
chore/next-16). -
Ask the user:
- the target version (default: latest 16.x, currently 16.4.3), and whether to stop after each major for review;
- where it's deployed (Vercel, another adapter, Docker or Node self-hosting, static export) and whether
middleware.tsrelies on the Edge runtime; - whether codemods may edit files (they do; run them with
--dryfirst when unsure); - whether network installs are approved. Follow the release-age cooldown in
core/supply-chain; a security patch inside the cooldown needs the user's explicit exception.
-
Plan the hops. Upgrade one major at a time: 13 → 14 → 15 → 16. Before each hop, move to the latest patch of the current major.
-
Plan React alongside each hop, using the matching major:
Next.js App Router needs Pages Router accepts Node 14.x React 18.2+ React 18.2+ ≥ 18.17 15.x React 19 React 18.2+ or 19 ≥ 18.18 16.x React 19 React 18.2+ or 19 ≥ 20.9 (use 22 or 24 LTS)
Steps
- Baseline. Run and record the results of a clean install, typecheck, lint, tests and
next build. If the baseline already fails, show the failures and ask whether to continue; never blame them on the upgrade later. - Patch the current major. For example, 14.x → 14.2.35 or 15.x → latest 15.5.x:
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.
- 3d ago First seen · 128 lines · 106 tokens per session scan A 9c3316fb0240
upgrade-nextjs is a skill published in the GitHub repository Phaedra-Solutions/cursor-rules (4 stars, last pushed 2d ago), licensed MIT. It adds 106 tokens to every session and 2,943 once invoked, about $0.0004 per session on Opus 5.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-11-01.
Other skills, from other repositories
grok-cli
Delegate bounded tasks to Grok Build from a supervising agent such as Codex. Use when the user asks Grok to investigate, review, implement, or provide another perspective, or when a distinct coding agent would materially help. Includes a background ACP client for progress, follow-up prompts, permissions, and…
documentation
Use when the user asks to install or maintain a documentation index, keep CLAUDE.md or AGENTS.md inventories synchronized with files, add document metadata, classify documentation, or apply documentation-only setup to a repository.
talk-like-scarletkc
A writing guide that makes text sound like the developer scarletkc, including posts, comments, technical opinions, project documents, and translations.
product-writing
Write, edit, or review UI copy, CLI messages, help text, code comments, and technical documentation covering product behavior, errors, status, setup, compatibility, or technical results.
marketing-copy
Write outbound promotional copy for a product or project: launch and update posts for community platforms and social media, store page descriptions and short blurbs, landing page headlines and calls to action, press-style announcements, and the naming of a product for another language or market. Covers what may be…
scoped-change
Judgment rules for locating the correct boundary of a requested change: staying inert outside it while completing every required site inside it. Use when scope is ambiguous, a diff touches neighboring surfaces, required dependent edits are unclear, or a proposed compatibility layer, migration, fallback, flag…