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 OutlineDriven/outline-driven-development --skill eslint-to-biome-migrationgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/eslint-to-biome-migration)<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.
<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>- 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.00068 | $0.01175 |
| Opus 5 | $0.00034 | $0.00588 |
| Sonnet 5 | $0.00014 | $0.00235 |
| Haiku 4.5 | $0.00007 | $0.00118 |
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.
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.jsonand 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
- 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. - Resolve Biome 2.5 with the package manager already pinned by the repository. Add
@biomejs/biomeas a development dependency. Do not change the package manager or introduce a second lockfile. Done when:@biomejs/biomeis added as a dev dependency with the existing package manager. - Read the installed Biome CLI help. Run its
migrate eslint --writecommand when ESLint configuration exists and itsmigrate prettier --writecommand when Prettier configuration exists. Merge both results into onebiome.jsonorbiome.jsonc; do not keep parallel configuration files. Done when: onebiome.jsonorbiome.jsoncexists with no parallel configuration files. - 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. - 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 bybiome check .; CI never uses--write. Done when: package scripts, hooks, and CI use Biome check with no--writein CI. - Run Biome once with
--write, inspect the diff, then runbiome 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. - After all checks pass, remove ESLint, Prettier, Standard, their plugins and shared configs,
.eslintrc*,eslint.config.*,.eslintignore,.prettierrc*,prettier.config.*, and package-leveleslintConfigorprettierfields. 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. - 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.
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.
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.
- 8d ago First seen · 44 lines · 68 tokens per session scan A d7fd296bd767
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.
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…
typescript-best-practices
TypeScript best practices. Use when reading or editing any .ts or .tsx file.
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.
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.
react-best-practices
React development guidelines with hooks, component patterns, state management, and performance optimization.
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"…