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 Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-eslintgit clone --depth 1 https://github.com/Postpartum-genushyacinthus29/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/postpartum-genushyacinthus29/dotnet-skills/dotnet-eslint)<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-eslint"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-eslint/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/postpartum-genushyacinthus29/dotnet-skills/dotnet-eslint"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-eslint.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.00053 | $0.01181 |
| Opus 5 | $0.00026 | $0.00590 |
| Sonnet 5 | $0.00011 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
dotnet-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 12d 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.
This is a copy
95% identical to dotnet-eslint — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 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
dotnet-stylelint - HTML-only checks on static output; route that to
dotnet-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.
Bootstrap When Missing
- Detect current state:
rg --files -g 'package.json' -g 'eslint.config.*' -g '.eslintrc*' -g 'tsconfig.json'rg -n '"eslint"|"@typescript-eslint"|"eslint-plugin-" --glob 'package.json' .
- Prefer a repo-local install:
npm install --save-dev eslint
- Add framework-specific plugins only when the repo actually uses the framework.
- Create or refine
eslint.config.jsoreslint.config.mjsinstead of leaving setup implicit. - Add repeatable commands to
AGENTS.mdandpackage.json, then verify with:npx eslint .npx eslint . --fix
- Return
status: configuredif the repo now has a working lint gate, orstatus: improvedif existing setup was tightened. - Return
status: not_applicableonly when another documented tool already owns JS or TS linting and migration is not requested.
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.
- 12d ago First seen · 106 lines · 53 tokens per session scan A 71387eaa7c18
dotnet-eslint is a skill published in the GitHub repository Postpartum-genushyacinthus29/dotnet-skills (10 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,181 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to dotnet-eslint, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
recipe-front-design
Execute from repository evidence through applicable UI Spec and optional ADR decisions to complete frontend Design Doc approval.
recipe-front-review
Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, then applies user-approved React corrections.
recipe-front-adjust
Adjust an already-implemented UI in-session with verification against the design source.
recipe-fullstack-implement
Orchestrate full-cycle implementation across backend and frontend layers.
recipe-front-plan
Create frontend work plan from design document and obtain plan approval.