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/biomejs/biome/changesetnpx skills add biomejs/biome --skill changesetgit clone --depth 1 https://github.com/biomejs/biomeWhat 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.00054 | $0.00723 |
| Opus 5 | $0.00027 | $0.00362 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
changeset 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changesets
Changesets describe user-visible behavior for release notes. Root AGENTS.md defines when automated contributions require one; CONTRIBUTING.md is canonical for package selection, versioning, branch targets, and prose format.
Decide Whether One Is Required
A changeset is required for behavior visible to users of the CLI, libraries, published crates, diagnostics, parser, formatter, linter, or assists.
No changeset is needed for an internal refactor with identical behavior, tests only, CI/build maintenance, or documentation-only edits.
Before opening a PR, explicitly confirm the user-facing classification as required by AGENTS.md. Do not infer user visibility only from the files changed.
Choose the Release Level
| Change | Level | Target |
|---|---|---|
| Bug fix or non-breaking behavior correction | patch |
main |
| New nursery lint rule | patch |
main |
| New user-facing feature or nursery promotion | minor |
next |
| Breaking user API change | major |
next |
Nursery rules are the exception to the usual new-feature mapping because they do not follow semantic versioning. Verify unusual cases against the current versioning policy.
Create the File
Run just new-changeset-empty to generate an empty file.
just new-changeset-empty
An empty generated entry starts with frontmatter delimiters. Replace that frontmatter with the package and release level rather than appending a second block:
---
"@biomejs/biome": patch
---
Description.
Use #### or ##### for headings inside a longer entry. Other heading levels interfere with changelog generation.
Write the Entry
- Describe user-visible behavior, not implementation.
- Use one to three sentences unless the impact genuinely needs an example.
- Use past tense for the contribution and present tense for resulting Biome behavior.
- Start bug fixes with the linked issue when one exists.
- Link rule and assist names to their Biome website pages.
- End every sentence with a full stop.
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 · 83 lines · 54 tokens per session scan A 1aaf64cff074
changeset is a skill published in the GitHub repository biomejs/biome (25,686 stars, last pushed 3d ago), licensed Apache-2.0. It adds 54 tokens to every session and 723 once invoked, about $0.0003 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
Biome
Biome 2.x — fast all-in-one web toolchain in Rust. Formats, lints, assists. Replaces Prettier + ESLint.
prettier-docs
Prettier 3.9.5 — opinionated code formatter. CLI, API, config, plugins, editor integration, CI.
chrome-release-verify
End-to-end Chrome security backport for an Electron release branch. Given a Chrome Releases blog URL and a branch (e.g. 41-x-y), determines which CVE fixes are missing from the actual synced source, writes the cherry-pick patches locally, validates them with e sync --3 + lint --patches, then pushes a single PR. Use…
ship
Land completed Fallow work after review, run pre-push parity, monitor merged-commit CI, and leave repositories clean. Use when asked to ship, merge, or move approved work to main.
electron-node-upgrade
Guide for performing Node.js version upgrades in the Electron project. Use when working on the roller/node/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Node.js changes, building, running the Node.js test suite, and proper commit…
electron-chromium-upgrade
Guide for performing Chromium version upgrades in the Electron project. Use when working on the roller/chromium/main branch to fix patch conflicts during e sync --3. Covers the patch application workflow, conflict resolution, analyzing upstream Chromium changes, and proper commit formatting for patch fixes.