oxlint-config

oxlint-config is a skill for Claude Code from danielbodnar/skills. It costs 21 tokens per session (819 once invoked), scanned A, original, MIT.

Configuration guidance for OxLint, a checker that finds likely bugs, TypeScript problems, import issues, and style problems in JavaScript and TypeScript code.

In plain words
What is it for?
Use it to install OxLint, create its configuration, enable its checks, and set project-wide linting defaults.
Why use it?
It provides consistent project checks and can automatically fix some reported issues, without manually assembling the configuration.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the code-quality plugin — 2 skills, 2 commands shipped together

Good fit Use it to install OxLint, create its configuration, enable its checks, and set project-wide linting defaults.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/danielbodnar/skills/oxlint-config
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 danielbodnar/skills --skill oxlint-config
Clone the repo
git clone --depth 1 https://github.com/danielbodnar/skills

Made for: Claude Code.

Or install code-quality, the plugin that ships this one along with the rest of its 2 skills, 2 commands.

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 oxlint-config

README.md
[![agentmods](https://agentmods.dev/badge/skills/danielbodnar/skills/oxlint-config.svg)](https://agentmods.dev/skills/danielbodnar/skills/oxlint-config)
Your own site
<a href="https://agentmods.dev/skills/danielbodnar/skills/oxlint-config"><img src="https://agentmods.dev/badge/skills/danielbodnar/skills/oxlint-config.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 819 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.
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.00021 $0.00819
Opus 5 $0.00010 $0.00409
Sonnet 5 $0.00004 $0.00164
Haiku 4.5 $0.00002 $0.00082

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

Security

Grade A, and why

oxlint-config 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.

plugins/code-quality/skills/oxlint-config/SKILL.md · 155 lines

How it starts

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

OxLint Configuration

OxLint is a high-performance linter for JavaScript and TypeScript, built on the oxc toolchain. It runs 50-100x faster than ESLint and provides a zero-config experience with sensible defaults.

Installation

Install OxLint as a dev dependency and generate the initial configuration:

bun i -D oxlint
bunx oxlint@latest --init --jsdoc-plugin --node-plugin --import-plugin

This generates .oxlintrc.json with the jsdoc, node, and import plugins enabled.

Create or update .oxlintrc.json in the project root with the following opinionated defaults:

{
  "$schema": "./node_modules/oxlint/configuration_schema.json",
  "rules": {
    "typescript": "all",
    "suspicious": "all",
    "correctness": "all",
    "style": "all",
    "pedantic": "warn"
  },
  "fix": true,
  "import-plugin": true,
  "jsdoc-plugin": true,
  "node-plugin": true
}

Rule Categories

  • typescript (all): Enforces TypeScript-specific best practices, catches type-related issues
  • suspicious (all): Flags code patterns that are likely bugs or unintended behavior
  • correctness (all): Catches definite errors and incorrect code
  • style (all): Enforces consistent code style conventions
  • pedantic (warn): Opinionated rules that may produce false positives; set to warn rather than error

Plugins

  • import-plugin: Validates import/export syntax, prevents misspelled paths and missing exports
  • jsdoc-plugin: Enforces JSDoc comment consistency and correctness
  • node-plugin: Catches common Node.js/Bun API misuse patterns

Package Scripts

Add linting scripts to package.json:

{
  "scripts": {
    "lint": "oxlint",
    "lint:fix": "oxlint --fix"
  }
}

Pre-Commit Hook Integration

Install husky and lint-staged:

bun i -D husky lint-staged

Initialize husky:

bunx husky init

Write the pre-commit hook file .husky/pre-commit:

bunx lint-staged

Read the full file on GitHub · 155 lines

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 · 155 lines · 21 tokens per session scan A 0f997562b32a

Subscribe to this mod's changes

oxlint-config is a skill published in the GitHub repository danielbodnar/skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 819 once invoked, about $0.0001 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-31.

Related

Other skills, from other repositories

debug-optimize-lcp

Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…

ChromeDevTools/chrome-devtools-mcp · 99 tokens

systematic-debugging

Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.

open-metadata/OpenMetadata · 37 tokens

diagnose

Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.

emdash-cms/emdash · 43 tokens

repro-admin

Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.

emdash-cms/emdash · 48 tokens

log-error-digest

Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…

zebbern/claude-code-guide · 71 tokens

byted-util-volcengine-detect-retry

An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.

bytedance/agentkit-samples · 101 tokens