Borrowing it
Nothing to install: this file belongs to managedcode/PrompterOne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/PrompterOne/main/.codex/skills/dotnet-webhint/SKILL.mdgit clone --depth 1 https://github.com/managedcode/PrompterOneWrote 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/prompterone/dotnet-webhint)<a href="https://agentmods.dev/skills/managedcode/prompterone/dotnet-webhint"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/dotnet-webhint/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/managedcode/prompterone/dotnet-webhint"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/dotnet-webhint.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.01104 |
| Opus 5.5 | $0.00021 | $0.00442 |
| Sonnet 5.5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
dotnet-webhint 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dotnet-webhint — 97% identical, 2 lines differ
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.
webhint for Browser-Facing Frontends in .NET Repositories
Trigger On
- the repo ships a browser-facing site and the user asks about accessibility, performance, SEO, security headers, or page quality
- the repo has
.hintrc,hintscripts, or a served local frontend that should be audited - the team needs more than syntax linting and wants runtime-oriented site checks
Do Not Use For
- JavaScript or TypeScript semantic linting; route that to
dotnet-eslintordotnet-biome - stylesheet-only linting; route that to
dotnet-stylelint - static HTML structure checks alone; route that to
dotnet-htmlhint
Inputs
- the nearest
AGENTS.md package.json.hintrcif present- the real audit target: local dev URL, preview URL, deployed URL, or built output
Workflow
- Choose the audit surface deliberately:
- running local URL such as
https://localhost:3000 - preview or deployed URL
- local connector against built output when no browser runtime is needed
- running local URL such as
- Prefer repo-local installation and a checked-in
.hintrc. - Start from a documented preset such as
web-recommended, then customize only for real repo requirements. - Add repeatable scripts to
package.json, for example:hint https://localhost:3000hint https://example.test --config .hintrc
- Keep runtime prerequisites explicit:
- supported Node.js version
- browser availability when the connector needs Chromium-based automation
- Treat findings as categorized work:
- headers and transport
- accessibility and HTML issues
- performance
- PWA and manifest signals
- Re-run the audit after fixes on the same URL or build output so results are comparable.
Bootstrap When Missing
- Detect current state:
rg --files -g 'package.json' -g '.hintrc*'rg -n '"hint"' --glob 'package.json' .
- Prefer a repo-local install:
npm install --save-dev hint
- Create or refine
.hintrcwith a known baseline such asweb-recommended. - Add repeatable commands to
AGENTS.mdandpackage.json, then verify with:npx hint https://localhost:3000npx hint -c ./.hintrc https://example.com
- Return
status: configuredif the repo now has a working site-audit gate, orstatus: improvedif the baseline was tightened. - Return
status: not_applicablewhen the repo does not expose a stable browser-facing surface that can be audited in the current task.
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.
- 1mo ago First seen · 106 lines · 53 tokens per session scan A b13bc00ea758
dotnet-webhint is a skill published in the GitHub repository managedcode/PrompterOne (45 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 1,104 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
maui-accessibility
Improve MAUI accessibility. USE FOR: semantic labels, hints, headings, screen-reader focus/announcements, AutomationProperties, touch targets, decorative content, TalkBack/VoiceOver/Narrator checks. DO NOT USE FOR: general layout, automation-only tests, performance.
polish-ui
Design-quality workflow that combines design taste, aesthetic direction, image-to-code, a Web Interface Guidelines audit, and real-browser verification. Use when building or polishing a UI surface, implementing a mockup/screenshot, or when asked to make a page "look great".
fin-arch-diagram
A tool for creating architecture diagrams, process flowcharts, and hierarchy trees. These show how system parts, business steps, decisions, or organizational levels relate to one another.
biome-creation
A workflow for placing rocks, trees, plants, and other reusable scene objects into a Unity biome, a themed area of a game world. It also covers regenerating the biome and checking the result with screenshots.
review-design
Reviews frontend components for design quality and UI/UX standards. Use when checking component styling, responsiveness, accessibility, or when asked to review a design.
lightningcad
Use when doing architectural facade panel layout and detailing in AutoCAD, ZWCAD or GstarCAD — panel numbering, shop drawing generation, material optimization. LightningCAD: building envelope detailing plugin for AutoCAD/ZWCAD/GstarCAD.