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/prisma/prisma-next/prisma-next-upgradenpx skills add prisma/prisma-next --skill prisma-next-upgradegit clone --depth 1 https://github.com/prisma/prisma-nextWrote 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/prisma/prisma-next/prisma-next-upgrade)<a href="https://agentmods.dev/skills/prisma/prisma-next/prisma-next-upgrade"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/prisma-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.00122 | $0.01912 |
| Opus 5 | $0.00061 | $0.00956 |
| Sonnet 5 | $0.00024 | $0.00382 |
| Haiku 4.5 | $0.00012 | $0.00191 |
Grade A, and why
prisma-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 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Prisma Next (user app)
This skill upgrades a project that consumes Prisma Next via the public package API (@prisma-next/postgres, @prisma-next/mongo, the contract files in prisma/, etc.). If the project is itself a Prisma Next extension, use the prisma-next-extension-upgrade skill instead — or both, if the repo contains both an app and an extension package.
Step 0 — Ensure the skill is up to date
Before anything else, ensure this skill is installed at @latest and reload it. Bug fixes to old per-transition upgrade instructions ship in the latest skill release as part of its cumulative set; running against a stale skill can apply a known-broken translation.
If the agent runtime supports an in-session refresh, perform it now. Otherwise, exit and ask the user to re-install (pnpm dlx skills add prisma/prisma-next/skills/upgrade --all), then re-invoke. The upgrade-skill subpath is intentionally unpinned (always main) — the cumulative instruction set is the source of truth, and the latest release fixes apply to every prior transition.
Pre-flight — extension compatibility
Before changing any code, refuse to upgrade past any installed extension's pinned Prisma Next version. Extensions in Prisma Next pin every @prisma-next/* dependency to a single exact version (no carets, no ranges); that pin is the highest version the extension has been validated against. Upgrading the user app past that pin would silently desynchronise the extension's type identity from the app's.
Steps:
- Read
prisma-next.config.ts(or its TS-discoverable equivalent at the project root) and enumerate the list of extension packages it imports. Eachextensions: [...]entry corresponds to an installed npm package. - For each extension, read its installed
package.jsonfromnode_modules/<extension-package-name>/package.jsonand find any@prisma-next/*entry underdependencies,peerDependencies, oroptionalDependencies. By construction those entries are exact-version pins (e.g."0.7.0"), set when the extension author last ran their own upgrade. - Compute the lowest pinned version across all extensions. That is the highest Prisma Next version reachable by this app on its current extension set.
- Compare to the user's target. If the target exceeds the lowest pin, halt with a structured message naming each lagging extension and its pinned version, and offer two paths:
- (a) Wait for the lagging extension to publish a compatible release, then re-run.
- (b) Re-run with
--to=<highest-reachable>(or whatever flag/option the user is using to set the target).
What ships with it
21 files 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.
- README.md 2.4 KB
- upgrades/0.10-to-0.11/instructions.md 1.9 KB
- upgrades/0.11-to-0.12/instructions.md 22 KB
- upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.ts 6.9 KB runs code
- upgrades/0.11-to-0.12/re-emit-domain-namespaced-contracts.ts 6.2 KB runs code
- upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts 6.2 KB runs code
- upgrades/0.11-to-0.12/strip-migration-labels-hints.ts 12 KB runs code
- upgrades/0.12-to-0.13/instructions.md 17 KB
- upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts 7.7 KB runs code
- upgrades/0.13-to-0.14/instructions.md 29 KB
- upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts 10 KB runs code
- upgrades/0.13-to-0.14/uuid-preset-rename.ts 1.3 KB runs code
- upgrades/0.14-to-0.15/instructions.md 20 KB
- upgrades/0.15-to-0.16/instructions.md 11 KB
- upgrades/0.16-to-0.17/instructions.md 29 KB
- upgrades/0.16-to-0.17/strip-sha256-hash-prefixes.ts 14 KB runs code
- upgrades/0.7-to-0.8/instructions.md 183 B
- upgrades/0.8-to-0.9/instructions.md 2.7 KB
- upgrades/0.8-to-0.9/strip-inline-contracts.ts 7.8 KB runs code
- upgrades/0.9-to-0.10/instructions.md 5.4 KB
- upgrades/0.9-to-0.10/stamp-storage-types-kind.ts 13 KB runs code
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 · 106 lines · 122 tokens per session scan A 96770e2a6413
prisma-next-upgrade is a skill published in the GitHub repository prisma/prisma-next (419 stars, last pushed 11d ago), licensed Apache-2.0. It adds 122 tokens to every session and 1,912 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-09-03.
Other skills, from other repositories
prisma-8
Comprehensive guide for building with Prisma 8 (Prisma Next), the contract-first data layer. Use whenever working on Prisma code in a project that uses it — authoring or editing the data contract (contract.prisma, PSL, TypeScript builders), migrations, queries (db.orm / db.sql), runtime wiring (db.ts, middleware…
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
record-upgrade-instructions
Record upgrade instructions alongside a Prisma Next breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma Next extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.