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/bumping-biomenpx skills add prisma/prisma-next --skill bumping-biomegit 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/bumping-biome)<a href="https://agentmods.dev/skills/prisma/prisma-next/bumping-biome"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/bumping-biome.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 | $0.00096 | $0.00379 |
| Opus 5 | $0.00048 | $0.00189 |
| Sonnet 5 | $0.00019 | $0.00076 |
| Haiku 4.5 | $0.00010 | $0.00038 |
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 yesterday.
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.
This is a copy
86% identical to bumping-biome — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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. -
Rename all
biome.jsonfiles tobiome.jsoncand replace the old package version number in$schemawith the newly installed package version number from the previous step. -
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.
- yesterday First seen · 27 lines · 96 tokens per session scan A 5274cf593f57
bumping-biome is a skill published in the GitHub repository prisma/prisma-next (419 stars, last pushed 10d ago), licensed Apache-2.0. It adds 96 tokens to every session and 379 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to bumping-biome, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
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.
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…
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.
github-review-iteration
Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating until actionable review items are cleared. Use when the user says “address PR review”, “triage review comments”, or “iterate until review is clean”.