Prisma ORM is a Node.js and TypeScript database toolkit that lets applications work with databases through a programming interface instead of writing every query directly in SQL. Developers use it with databases including PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB, and CockroachDB. The catalogue add-ons provide agent rules, skills, hooks, agents, and other workflows for using Prisma.
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 prisma/orm --skill bumping-biomegit clone --depth 1 https://github.com/prisma/ormWrote 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/orm/bumping-biome)<a href="https://agentmods.dev/skills/prisma/orm/bumping-biome"><img src="https://agentmods.dev/badge/skills/prisma/orm/bumping-biome/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/prisma/orm/bumping-biome"><img src="https://agentmods.dev/badge/skills/prisma/orm/bumping-biome.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector pass
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.00096 | $0.00391 |
| Opus 5.5 | $0.00038 | $0.00156 |
| Sonnet 5.5 | $0.00019 | $0.00078 |
| Haiku 4.5 | $0.00010 | $0.00039 |
Grade A, and why
bumping-biome 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bumping-biome — 86% identical, 2 lines differ
What it actually says
Bumping Biome Skill
Instructions
-
Run
pnpm up -D -w -r @biomejs/biome@<version>- replace<version>with a specific package version provided in the session, otherwise fallback tolatest. -
If any
biome.jsonfiles remain, rename them tobiome.jsonc. Then replace the old package version number in$schemawith the newly installed package version number from the previous step, in everybiome.jsonc. -
Run
pnpm -w lint:fix. Report any issues/regressions briefly. -
If there are remaining unsafe fixes following the previous step, offer to run
pnpm -w lint:fix:unsafeto attempt to fix some of the issues/regressions. -
If the offer in the previous step is agreed, run the appropriate command, and report any remaining issues/regressions briefly.
-
If there are remaining issues/regressions after the previous step, try and come up with your own suggestions for fixing them and present the plan.
Don't Do
-
Don't scan for
biomeversions. If the session doesn't include a specific package version number, uselatest. -
Don't read the root
package.jsonor lockfiles looking for the currentbiomeversion/s. We'll see the change in version numbers in Git anyway.
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.
- 1mo ago First seen · 27 lines · 96 tokens per session scan A 6210e06069a6
bumping-biome is a skill published in the GitHub repository prisma/orm (47,697 stars, last pushed today), licensed Apache-2.0. It adds 96 tokens to every session and 391 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-09-03.
Other skills, from other repositories
prisma-orm
Use when modeling data or writing type-safe queries with Prisma ORM in TypeScript — schema.prisma, prisma.config.ts, the generated Prisma Client, and Prisma Migrate, including the v6 to v7 upgrade. NOT schema-as-TS with a SQL builder (that is drizzle-orm), NOT ORM-agnostic zero-downtime migration (that is…
adding-personhog-rpc
Guide for adding a new RPC to personhog-replica and personhog-router. Covers eligibility checks, proto definition, code generation for Python and Node.js clients, Rust implementation (storage trait, postgres queries, service handler, router wiring), and index compatibility validation. Use when adding a new gRPC…
typescript-expert
Expert-level TypeScript development with modern tooling, advanced types, and best practices. Use this skill for TypeScript projects requiring type-safe code, modern bundling, and comprehensive testing.
using-prisma
Prisma 5+ ORM with schema-first design, type-safe client, migrations, and database integrations (Supabase, PlanetScale, Neon). Use for TypeScript/JavaScript database access.
api-first
Maintain the OpenAPI contract in docs, regenerate TypeScript types into src/generated/api, and wire client/server imports without hand-editing generated files.
javascript-typescript
Modern JavaScript and TypeScript development patterns.