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-htmlhintgit 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-htmlhint)<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-htmlhint"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-htmlhint/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-htmlhint"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-htmlhint.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.00048 | $0.01071 |
| Opus 5 | $0.00024 | $0.00535 |
| Sonnet 5 | $0.00010 | $0.00214 |
| Haiku 4.5 | $0.00005 | $0.00107 |
Grade A, and why
dotnet-htmlhint 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 11d 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
86% identical to htmlhint — 10 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTMLHint for Static HTML in .NET Repositories
Trigger On
- the repo has static HTML files, generated frontend output, or standalone templates under
wwwroot/,dist/, or other web folders - the user asks for HTML structure checks, invalid attribute detection, or basic DOM-quality linting
- the repo wants a narrow HTML gate separate from JS, CSS, and full-site runtime audits
Do Not Use For
- raw
.cshtmlor.razorsource with server-side directives; lint the rendered or published output instead - JavaScript or TypeScript linting; route that to
dotnet-eslint - runtime performance, accessibility, SEO, or headers; route that to
dotnet-webhint
Inputs
- the nearest
AGENTS.md package.json.htmlhintrcor equivalent config if present- the real static HTML target: source templates, built output, or deployed URL
Workflow
- Choose the right target first:
- static HTML source files
- generated build output such as
dist/ - a reachable URL when the page is already served
- Prefer repo-local installation and checked-in config for repeatable runs.
- Keep HTMLHint focused on static HTML correctness and lightweight policy.
- Add narrow scripts to
package.json, for example:htmlhint "dist/**/*.html"htmlhint "wwwroot/**/*.html"
- If the repo has templating syntax that confuses the parser, lint the rendered output instead of forcing source templates through the tool.
- Use rule overrides deliberately for real project conventions; do not disable broad classes of checks just to make a noisy first pass green.
- Rerun the publish or frontend build flow if fixes touched generated or packaged HTML sources.
Bootstrap When Missing
- Detect current state:
rg --files -g 'package.json' -g '.htmlhintrc*' -g '*.html'rg -n '"htmlhint"' --glob 'package.json' .
- Prefer a repo-local install:
npm install --save-dev htmlhint
- Add or refine
.htmlhintrconly after confirming the actual target files. - Add repeatable commands to
AGENTS.mdandpackage.json, then verify with:npx htmlhint "dist/**/*.html"npx htmlhint https://example.com
- Return
status: configuredif HTMLHint now owns a clear static-HTML gate, orstatus: improvedif the existing setup was tightened. - Return
status: not_applicablewhen the repo's HTML is primarily server-rendered templates that should be validated after rendering instead.
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.
- 11d ago First seen · 101 lines · 48 tokens per session scan A 5cf2b8d0c451
dotnet-htmlhint is a skill published in the GitHub repository Postpartum-genushyacinthus29/dotnet-skills (10 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,071 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to htmlhint, differing in 10 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.