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 agentmods add skills/managedcode/prompterone/dotnet-webhintnpx skills add managedcode/PrompterOne --skill dotnet-webhintgit clone --depth 1 https://github.com/managedcode/PrompterOneWhat 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 | $0.00053 | $0.01104 |
| Opus 5 | $0.00026 | $0.00552 |
| Sonnet 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 2d 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 — 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.
- 2d ago First seen · 106 lines · 53 tokens per session scan A b13bc00ea758
dotnet-webhint is a skill published in the GitHub repository managedcode/PrompterOne (42 stars, last pushed 3mo ago), licensed MIT. It adds 53 tokens to every session and 1,104 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-30.
Other skills, from other repositories
vela
Compiler-exact code search for .NET solutions - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Covers C#, VB, Razor Pages, MVC views and Blazor components, which grep and every other code-intelligence tool miss. Deterministic, built on Roslyn, never modifies the…
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
dotnet-blazor-audit
.NET Blazor 安全审计 skill。覆盖 Blazor Server / Blazor WebAssembly 的 Circuit 生命周期、JS Interop、组件渲染、事件处理、状态管理、SignalR 底层连接。追踪用户可控输入到 DOM 操作、命令执行、文件操作等 sink，输出 XSS、信息泄露和 RCE 证据。.
html-to-ugui
HTML 原型转 Unity UGUI 智能 Prefab 生成管线。通过 AI 生成符合 UI-DSL 的 HTML，用 Playwright/浏览器烘焙 JSON v2 坐标、图片和适配意图，再导入 Unity 由 HtmlToUGUIBaker 生成可维护、多终端适配的 UGUI Prefab。触发场景：(1) 需要从自然语言生成 Unity UGUI 界面 (2) 需要从 HTML 原型烘焙 UGUI (3) UI 中包含图片并希望一键导入/绑定 Sprite (4) 需要 PC/mobile/pad 多终端适配 Prefab。.
webgpu-threejs-tsl
Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, TSL syntax and node materials, compute shaders, post-processing effects, and WGSL integration. Use this skill when working with Three.js WebGPU, TSL shaders, node materials, or…
widget-creator
Step-by-step guide for creating new widgets in the Hex1b TUI library. Use when implementing new widgets from scratch, including widget records, nodes, extension methods, theming, reconciliation, and tests.