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/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/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/prisma-next/bumping-biome"><img src="https://agentmods.dev/badge/skills/prisma/prisma-next/bumping-biome.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.00096 | $0.00379 |
| Opus 5.5 | $0.00038 | $0.00152 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 27 lines · 96 tokens per session scan A 5274cf593f57
bumping-biome is a skill published in the GitHub repository prisma/prisma-next (414 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 379 once invoked, about $0.0004 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…