What is dotnet-metalint?

A guide for using Metalint as one command that runs several frontend code checkers in a .NET repository. These checkers can cover JavaScript or TypeScript, CSS, and HTML.

Use it when a repository needs one lint command for tools such as ESLint, Stylelint, and HTMLHint, with shared configuration under .metalint/.

It coordinates existing linters without hiding which tool owns each type of file, making frontend checks easier to run consistently.

dotnet-metalint — Skill for Claude Code and Codex by Postpartum-genush

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 Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-metalint

Clone the repo

git clone --depth 1 https://github.com/Postpartum-genushyacinthus29/dotnet-skills

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-metalint/github.svg)](https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-metalint)

Your own site

<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-metalint"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-metalint/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-metalint"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-metalint.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,099 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.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01099
Opus 5	$0.00032	$0.00549
Sonnet 5	$0.00013	$0.00220
Haiku 4.5	$0.00006	$0.00110

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

Security

Grade A, and why

dotnet-metalint 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.

skills/dotnet-metalint/SKILL.md · 104 lines

How it starts

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

Metalint for Aggregated Frontend Linting in .NET Repositories

Trigger On

the repo wants one command to run several frontend linters together
the user asks for a unified lint entrypoint over ESLint, Stylelint, HTMLHint, or similar tools
the repo already has multiple linters and the problem is orchestration rather than choosing a single owner

Do Not Use For

simple repos where one tool such as Biome already covers the required surface
teams that have not decided which underlying linters own JS, CSS, and HTML yet
replacing the underlying linter configs with one vague wrapper config

Inputs

the nearest AGENTS.md
package.json
existing linter configs
any .metalint/ directory already checked in

Workflow

Define underlying ownership first:
- ESLint for JS or TS
- Stylelint for CSS or SCSS
- HTMLHint for static HTML
- other delegated linters only when the repo really uses them
Use Metalint only after those owners are explicit.
Keep all wrapper configuration under .metalint/ and keep the delegated configs reviewable.
Add package scripts such as:
- lint: metalint
- lint:fix: metalint --fix
Treat formatter overlap carefully. If delegated tools can all fix files, define which ones are allowed to mutate which globs.
Use Metalint in CI when the repo benefits from a single frontend lint step and formatter output such as GitHub annotations.
Re-run the underlying owners directly when debugging Metalint issues so failures stay attributable.

Bootstrap When Missing

Detect current state:
- rg --files -g 'package.json' -g '.metalint/**' -g 'eslint.config.*' -g 'stylelint.config.*' -g '.htmlhintrc*'
- rg -n '"metalint"|"eslint"|"stylelint"|"htmlhint"' --glob 'package.json' .
Prefer a repo-local install:
- npm install --save-dev metalint
Install the delegated linters the repo actually needs; Metalint does not replace them.
Create .metalint/metalint.config.js plus delegated config files under .metalint/ only when the repo wants that consolidated layout.
Verify with:
- npx metalint
- npx metalint --fix
Return status: configured if the repo now has a working aggregated entrypoint, or status: improved if orchestration was tightened.
Return status: not_applicable when the repo intentionally stays with direct linter commands and does not want the wrapper layer.

Read the full file on GitHub · 104 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.

12d ago First seen · 104 lines · 63 tokens per session scan A c4954d27074c

Subscribe to this mod's changes

dotnet-metalint is a skill published in the GitHub repository Postpartum-genushyacinthus29/dotnet-skills (10 stars, last pushed 2d ago), licensed MIT. It adds 63 tokens to every session and 1,099 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.

Frontend agent-skills ai-agents alexa-skills-sdk aws-lambda azure-openai code-analysis-true code-quality

dotnet-metalint

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Metalint for Aggregated Frontend Linting in .NET Repositories

Trigger On

Do Not Use For

Inputs

Workflow

Bootstrap When Missing

What this file has done since we first saw it

Other skills, from other repositories

frontend-ai-guide

recipe-front-design

recipe-front-review

recipe-front-adjust

recipe-fullstack-implement

recipe-front-plan