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 managedcode/dotnet-skills --skill eslintgit clone --depth 1 https://github.com/managedcode/dotnet-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/managedcode/dotnet-skills/eslint)<a href="https://agentmods.dev/skills/managedcode/dotnet-skills/eslint"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/eslint.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 62 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 63 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00131 | $0.01395 |
| Opus 5 | $0.00066 | $0.00698 |
| Sonnet 5 | $0.00026 | $0.00279 |
| Haiku 4.5 | $0.00013 | $0.00139 |
Grade A, and why
eslint 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 5d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ESLint for Frontend Assets in .NET Repositories
Trigger On
- the repo has
package.json,eslint.config.*,.eslintrc*,tsconfig.json, or JS/TS/React frontend files - the user asks for JavaScript or TypeScript linting, React rule enforcement, import hygiene, or unsafe frontend patterns
- CI should fail on frontend lint findings instead of relying on editor-only feedback
Do Not Use For
- CSS ownership by itself; route that to
stylelint - HTML-only checks on static output; route that to
htmlhint - repos that intentionally standardized on Biome as the only JS or TS formatter-linter, unless migration or comparison is explicitly requested
Inputs
- the nearest
AGENTS.md package.jsoneslint.config.*or.eslintrc*tsconfig.jsonwhen TypeScript or type-aware rules are involved
Workflow
- Detect ownership first:
- existing ESLint config
- package manager and workspace layout
- framework packages such as React, Next.js, Vue, or plain TypeScript
- Keep ESLint as the semantic lint owner for JS and TS files when the repo needs rich plugin ecosystems or framework-specific rules.
- Prefer checked-in local devDependencies over global installs so CI and local runs match.
- Add narrow scripts to
package.json, for example:lint:eslint .lint:fix:eslint . --fix
- Scope auto-fix runs before broad rewrites:
- fix a bounded folder or glob first
- rerun the linter
- rerun the frontend build or tests if the repo has them
- If the repo wants type-aware rules, verify the target files are covered by the intended
tsconfig.jsonbefore enabling heavier rules. - Do not hide noise by mass-disabling rules. Fix code, narrow scope, or phase severity deliberately.
Current Upstream Notes
- ESLint
v10.9.1includes thev10.8.1autofix and false-positive corrections and fixesno-loss-of-precisionso numeric literals with a trailing decimal point are not reported incorrectly. Re-run focused rule fixtures before retaining a suppression for that syntax. - Re-run the real lint suite and autofix snapshots before accepting churn, especially in semicolon-free code or generated output. Keep the
v10.8.0flat-config type exports and formatter changes in mind when updating tooling integrations. - Current docs clarify parser option precedence over
languageOptionsand document the v9/v10 migration codemods; review flat-config migrations that mix legacy parser settings with new config shapes.
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.
- 5d ago First seen · 110 lines · 131 tokens per session scan A 8fb517d9d2e7
eslint is a skill published in the GitHub repository managedcode/dotnet-skills (477 stars, last pushed 3d ago), licensed MIT. It adds 131 tokens to every session and 1,395 once invoked, about $0.0007 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
winui-design
Use when designing, reviewing, or fixing WinUI 3: sample and control discovery with winapp find-ui, layout planning, control choice, Fluent Design alignment, Light/Dark/High Contrast theming, typography, spacing, brushes, accessibility, and XAML data-binding design. Load before authoring new XAML, reviewing UI PRs…
winui-wpf-migration
Migrate WPF applications to WinUI 3 — namespace replacement (System.Windows → Microsoft.UI.Xaml), control mapping (DataGrid→ListView, WrapPanel→ItemsRepeater, TabControl→TabView), threading (Dispatcher→DispatcherQueue), imaging (System.Drawing→BitmapImage), MVVM conversion to CommunityToolkit.Mvvm, and…
aksel-builder
Expert builder for Aksel, the Nav / @navikt design system — React components, design tokens, layout primitives, theming (light/dark), icons, CSS, the Tailwind preset, version migrations, Figma-to-code. Triggers — Aksel, "using/with aksel", Nav/Navikt, "designsystemet", "design system", @navikt/ds- (e.g.…
nav-dekoratoren
Integrer og konfigurer Nav Dekoratøren – felles header og footer for nav.no-applikasjoner. Bruk når et team skal ta i bruk Dekoratøren, oppdatere konfigurasjon, legge til breadcrumbs/språkvelger/analytics, håndtere samtykke (ekomloven), CSP eller feilsøke integrasjon mot dekoratøren.
aksel-spacing
Lag responsive layouts med Aksel Design System (v8+) - spacing tokens, layout primitives (Box, HStack, VStack, HGrid, Page, Bleed) og ResponsiveProp.
web-design-reviewer
Visuell inspeksjon av nettsider for å identifisere og fikse designproblemer. Trigges av forespørsler som "sjekk designet", "gå gjennom UI-en", "fiks layouten", "finn designfeil". Finner problemer med responsivt design, tilgjengelighet, visuell konsistens og layout, og fikser dem i kildekoden.