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 neverinfamous/memory-journal-mcp --skill next-upgradegit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/next-upgrade)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/next-upgrade"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/next-upgrade.svg" alt="Measured on agentmods" 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.00075 | $0.00507 |
| Opus 5 | $0.00037 | $0.00253 |
| Sonnet 5 | $0.00015 | $0.00101 |
| Haiku 4.5 | $0.00007 | $0.00051 |
Grade A, and why
next-upgrade 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 8d 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.
What it actually says
Upgrade Next.js
Upgrade the current project to a targeted Next.js version following official migration guides.
Instructions
-
Detect current environment:
- Read
package.jsonto identify the current Next.js version, React version, and package manager (npm,pnpm,yarn). - Read the lockfile to ensure you use the correct package manager.
- Read
-
Determine target version:
- Do NOT blindly use
@latest. Always determine the explicit target version (e.g.,15.0.0) based on user request or current LTS. - For major version jumps, upgrade incrementally (e.g., 13 → 14 → 15).
- Do NOT blindly use
-
Consult Upgrade Decision Tree:
- Read references/decision-tree.md to find the correct codemods and checklists for your target version.
-
Security Gate:
- You MUST request explicit user confirmation before running any codemod that modifies source files.
-
Run codemods FIRST (before installing new versions):
- Next.js codemods should often be run against the old codebase before upgrading to automate breaking changes.
- Example:
npx @next/codemod@<target-version> <transform> <path>
-
Pin dependencies:
- Upgrade Next.js and peer dependencies to the specific target version:
- Example:
pnpm install [email protected] [email protected] [email protected]
-
Review Diff:
- After running codemods and installing new dependencies, you MUST run
git diffor review the changes. - Do NOT commit or ship without explicit user review of the codemod changes.
- After running codemods and installing new dependencies, you MUST run
-
Test the upgrade:
- Run
npm run build(or equivalent) to check for build errors. - If there are errors in
next.config.jsor routing, resolve them manually.
- Run
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.
- 8d ago First seen · 44 lines · 75 tokens per session scan A 2ebc59d5d7e1
next-upgrade is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 507 once invoked, about $0.0004 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
framework-expert
Unified framework expertise bundle. Lazy-loads relevant framework patterns (React, Vue, Angular, Next.js, Node.js, Python, Laravel, Go, Flutter, React Native, TypeScript) based on detected tech stack.
design-expert
UI/UX design expertise — component design, design system selection, responsive layout. Includes auto-detection from package.json and Context7 integration for library docs.
design-tokens
Generate a cohesive color-token system from ONE OKLCH brand hue — primary/secondary/background/foreground/muted/border with semantic light + dark, emitted as a Tailwind v4 @theme block or a CSS-variables fallback. Use when starting a design system, defining brand colors, setting up theming/dark-mode, or replacing…
motion-design
Restrained, accessible web motion — Framer Motion declarative patterns and CSS-only staggered reveals for high-impact moments, always bundle-aware and reduced-motion-safe. Use when adding animation/transitions to a UI (entrance reveals, list stagger, page/route transitions, micro-interactions) or when motion feels…
frontend-aesthetics
Anti-AI-slop taste layer for UI output — distinctive typography, dominant+accent color hierarchy, and implementation-matched polish. Use when building or restyling a UI/landing/component that should look designed rather than defaulted, or when the user asks for something 'beautiful', 'distinctive', 'less generic', or…
maintain-splash-pages
The Lossless Group's pattern for repo-level splash pages — small Astro sites at /splash/ that ship to GitHub Pages on push to main, render the repo's changelog/ + context-v/ alongside curated marketing copy, and stay isolated from any package the repo also publishes. Use proactively whenever scaffolding a noteworthy…