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 dallay/agents-skills --skill eslint-configgit clone --depth 1 https://github.com/dallay/agents-skillsWrote 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/dallay/agents-skills/eslint-config)<a href="https://agentmods.dev/skills/dallay/agents-skills/eslint-config"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/eslint-config/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/dallay/agents-skills/eslint-config"><img src="https://agentmods.dev/badge/skills/dallay/agents-skills/eslint-config.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.00068 | $0.01685 |
| Opus 5 | $0.00034 | $0.00843 |
| Sonnet 5 | $0.00014 | $0.00337 |
| Haiku 4.5 | $0.00007 | $0.00169 |
Grade A, and why
eslint-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 10d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to Use
- Setting up ESLint from scratch using the modern flat config format (
eslint.config.js). - Migrating a project from legacy
.eslintrc.*to flat config. - Configuring TypeScript-ESLint for strict type-checked linting.
- Writing custom ESLint rules or shareable config packages.
- Resolving rule conflicts between ESLint, Prettier, and framework-specific plugins.
- Optimizing linting performance for large monorepos.
Critical Patterns
- Flat Config Only: Always use
eslint.config.js(or.mjs/.mts). The legacy.eslintrc.*format is deprecated since ESLint v9. Do NOT create new projects with.eslintrc. - Explicit Over Implicit: Flat config has no implicit inheritance. Every config object in the array is applied in order — later entries override earlier ones.
- TypeScript Requires Parser: Always pair
@typescript-eslint/parserwith@typescript-eslint/eslint-plugin. Use type-checked rules (strictTypeChecked) for maximum safety. - Severity Consistency: Use
"error"for rules that must block CI,"warn"for progressive adoption, and"off"to explicitly disable inherited rules. Never leave rules ambiguous. - Ignore via Config: Use the
ignoresproperty in flat config instead of.eslintignorefiles. Global ignores go in a config object with only theignoreskey. - Plugin Namespacing: In flat config, plugins are objects, not strings. Import the plugin and assign it to a namespace key to avoid collisions.
- Performance: Use
--cachein CI and locally. For monorepos, scope linting to changed files with--no-error-on-unmatched-pattern.
Code Examples
Modern Flat Config (eslint.config.js)
import js from "@eslint/js";
import tseslint from "typescript-eslint";
import prettier from "eslint-config-prettier";
export default tseslint.config(
// Global ignores — standalone object with ONLY ignores key
{
ignores: ["dist/", "node_modules/", "coverage/", "**/*.generated.*"],
},
// Base JS recommended rules
js.configs.recommended,
// TypeScript strict + type-checked rules
...tseslint.configs.strictTypeChecked,
...tseslint.configs.stylisticTypeChecked,
// TypeScript parser options — applies to all TS files
{
languageOptions: {
parserOptions: {
projectService: true,
tsconfigRootDir: import.meta.dirname,
},
},
},
// Disable type-checked rules for JS files (config files, scripts)
{
files: ["**/*.js", "**/*.mjs"],
...tseslint.configs.disableTypeChecked,
},
// Project-specific overrides
{
files: ["src/**/*.ts"],
rules: {
"@typescript-eslint/no-unused-vars": [
"error",
{ argsIgnorePattern: "^_", varsIgnorePattern: "^_" },
],
"@typescript-eslint/explicit-function-return-type": "error",
"@typescript-eslint/no-floating-promises": "error",
"@typescript-eslint/strict-boolean-expressions": "warn",
},
},
// Test file relaxations
{
files: ["**/*.test.ts", "**/*.spec.ts"],
rules: {
"@typescript-eslint/no-explicit-any": "off",
"@typescript-eslint/no-non-null-assertion": "off",
"@typescript-eslint/no-unsafe-assignment": "off",
},
},
// Prettier must be LAST to override formatting rules
prettier,
);
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.
- 10d ago First seen · 231 lines · 68 tokens per session scan A e9e971bfc93a
eslint-config is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 18d ago), licensed MIT. It adds 68 tokens to every session and 1,685 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-31.
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…
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.
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.
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.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.