eslint-to-biome-migration

eslint-to-biome-migration is a skill for Codex from OutlineDriven/outline-driven-development. It costs 68 tokens per session (1,175 once invoked), scanned A, original, Apache-2.0.

A migration workflow that moves a JavaScript or TypeScript project from ESLint, Prettier, Standard, or mixed legacy settings to Biome 2.5. Biome is a tool for checking and formatting code.

In plain words
What is it for?
Use it to update linting and formatting configuration, scripts, dependencies, hooks, and CI for a Biome-based setup.
Why use it?
It removes overlapping old configuration and dependencies while preserving the intended checks in local development, hooks, and CI.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to update linting and formatting configuration, scripts, dependencies, hooks, and CI for a Biome-based setup.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/outline-driven-development/eslint-to-biome-migration
Install

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.

Any agent
npx skills add OutlineDriven/outline-driven-development --skill eslint-to-biome-migration
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/outline-driven-development

Made for: Codex.

Wrote 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.

agentmods badge for eslint-to-biome-migration

README.md
[![agentmods](https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/eslint-to-biome-migration/github.svg)](https://agentmods.dev/skills/outlinedriven/outline-driven-development/eslint-to-biome-migration)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/eslint-to-biome-migration"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/eslint-to-biome-migration/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.

agentmods 80×15 button for eslint-to-biome-migration

Your own site · 80×15
<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/eslint-to-biome-migration"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/eslint-to-biome-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,175 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00068 $0.01175
Opus 5 $0.00034 $0.00588
Sonnet 5 $0.00014 $0.00235
Haiku 4.5 $0.00007 $0.00118

Measured 8d ago against content hash d7fd296bd767, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

eslint-to-biome-migration 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 8d 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.

.devin/skills/eslint-to-biome-migration/SKILL.md · 44 lines

How it starts

The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ESLint to Biome migration

Contract

Field Bound contract
Trigger Migrate an existing JavaScript or TypeScript project from ESLint, Prettier, Standard, or mixed lint configuration to Biome 2.5.
Authority Reversible local writes only. Edit lint configuration, package scripts, dependencies, hooks, and CI checks. Roll back with version control.
Side effect Writes biome.json or biome.jsonc; removes superseded lint and format configuration and dependencies; updates local scripts, hooks, and CI. No remote mutation.
Done Biome 2.5 lint and format checks pass; the prior lint and format checks have an explicit coverage disposition; no ESLint, Prettier, Standard, or legacy config remains; CI runs Biome without auto-fix and passes.

Inputs

  • Project root with package.json and an existing lint or format setup. Required.
  • Existing package manager and lockfile. Required; keep the manager fixed during this lint-only migration.
  • CI and hook configuration paths. Optional; detect them when present.

Procedure

  1. Bound the migration. Read package.json, the lockfile, all ESLint, Prettier, Standard, and Biome configuration, package scripts, hook configuration, and CI lint steps. Run the existing lint and format checks without auto-fix. Record each command, exit code, and finding count. Done when: all configuration is read and existing checks are recorded with exit codes and finding counts.
  2. Resolve Biome 2.5 with the package manager already pinned by the repository. Add @biomejs/biome as a development dependency. Do not change the package manager or introduce a second lockfile. Done when: @biomejs/biome is added as a dev dependency with the existing package manager.
  3. Read the installed Biome CLI help. Run its migrate eslint --write command when ESLint configuration exists and its migrate prettier --write command when Prettier configuration exists. Merge both results into one biome.json or biome.jsonc; do not keep parallel configuration files. Done when: one biome.json or biome.jsonc exists with no parallel configuration files.
  4. Reconcile coverage. Map each project-specific legacy rule or override to a Biome rule, formatter option, file include, or ignore. Mark an unsupported rule as unsupported: <rule> — <observable risk> before removal. Do not claim parity from equal issue counts alone. Done when: every legacy rule or override has a Biome disposition or an unsupported marker with observable risk.
  5. Replace package scripts with "check": "biome check ." and "check:fix": "biome check --write .", preserving unrelated scripts. Replace hook and CI lint commands with the repository package runner followed by biome check .; CI never uses --write. Done when: package scripts, hooks, and CI use Biome check with no --write in CI.
  6. Run Biome once with --write, inspect the diff, then run biome check . without mutation. Run the repository type check, tests, and build because formatting can expose parse or generated-file defects. Done when: biome check . passes without mutation and type check, tests, and build pass.
  7. After all checks pass, remove ESLint, Prettier, Standard, their plugins and shared configs, .eslintrc*, eslint.config.*, .eslintignore, .prettierrc*, prettier.config.*, and package-level eslintConfig or prettier fields. Preserve an ignore only by moving its pattern into Biome configuration first. Done when: no ESLint, Prettier, Standard, or legacy config or dependency remains and preserved ignores are moved into Biome configuration.
  8. Reinstall from the lockfile, rerun Biome, type check, tests, build, and the exact CI lint command, then scan manifests and configuration for a live reference to a removed package or config. Done when: reinstall succeeds, all checks pass, and no live reference to a removed package or config remains.

Read the full file on GitHub · 44 lines

Files

What ships with it

1 file 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.

Changes

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.

  1. 8d ago First seen · 44 lines · 68 tokens per session scan A d7fd296bd767

Subscribe to this mod's changes

eslint-to-biome-migration is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 6d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,175 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-09-03.

Related

Other skills, from other repositories

onejs-setup-and-overview

Use this skill whenever the user wants to build or set up user interface in a Unity project using OneJS, React, TypeScript, or JSX, e.g. 'add a main menu to my game', 'build a settings screen', 'make a HUD', 'set up OneJS', 'my OneJS panel is blank', 'the UI is not hot reloading'. Covers confirming OneJS is installed…

Singtaa/OneJS · 199 tokens

typescript-best-practices

TypeScript best practices. Use when reading or editing any .ts or .tsx file.

cursor/plugins · 24 tokens

senior-frontend

Frontend development for React 19, Next.js 15, TypeScript, and Tailwind CSS v4 / Pengembangan frontend dengan React 19, Next.js 15, TypeScript, dan Tailwind CSS v4.

roedyrustam/vibes-plug · 50 tokens

react-component-design

Designs or reviews React component APIs. Handles prop drilling decisions, composition patterns, controlled/uncontrolled contracts, and minimal public API surfaces for React 18+ TypeScript components. Invoked when creating new components, refactoring existing ones, or reviewing component contracts.

soulcodex/agentic · 56 tokens

react-best-practices

React development guidelines with hooks, component patterns, state management, and performance optimization.

myths-labs/muse · 22 tokens

modernize-ui5-app

Convert a legacy UI5 freestyle JavaScript app (sync bootstrap, jQuery.sap., ES5, sapbelize) into a modern UI5 1.147 TypeScript app with sap.f.FlexibleColumnLayout, typed event handlers, ES modules, BaseController, and saphorizon — with 5 documented critical traps up front. Use when asked to "modernize this UI5 app"…

arc-mcp/arc-1 · 118 tokens