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 FritzAndFriends/BlazorWebFormsComponents --skill documentationgit clone --depth 1 https://github.com/FritzAndFriends/BlazorWebFormsComponentsWrote 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/fritzandfriends/blazorwebformscomponents/documentation)<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/documentation"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/documentation/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/fritzandfriends/blazorwebformscomponents/documentation"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/documentation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 214 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00119 | $0.05172 |
| Opus 5.5 | $0.00048 | $0.02069 |
| Sonnet 5.5 | $0.00024 | $0.01034 |
| Haiku 4.5 | $0.00012 | $0.00517 |
Grade A, and why
documentation 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.
How it starts
The opening of the file, as written. The whole thing — 730 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Skill for BlazorWebFormsComponents
This skill provides guidance for writing documentation for the BlazorWebFormsComponents library. Use this when creating or updating component documentation, migration guides, or utility feature docs.
Documentation Philosophy
The documentation serves developers migrating ASP.NET Web Forms applications to Blazor. Every document should:
- Help developers understand what IS and ISN'T supported
- Show side-by-side Web Forms → Blazor syntax comparisons
- Provide practical, copy-paste-ready examples
- Link to original Microsoft documentation for reference
Component Documentation Template
When documenting a component, use this exact structure:
# [ComponentName]
[One paragraph describing what this component does and why it exists in this library]
Original Microsoft implementation: https://docs.microsoft.com/en-us/dotnet/api/system.web.ui.webcontrols.[componentname]?view=netframework-4.8
## Features Supported in Blazor
- [List each supported feature as a bullet point]
- [Include supported events with brief description]
- [Note any Blazor-specific enhancements]
### Blazor Notes
[Any Blazor-specific implementation details or behavioral differences]
## Web Forms Features NOT Supported
- **[FeatureName]** - [Brief explanation of why not supported or what to use instead]
- **PostBackUrl** - Not supported; Blazor uses component events instead
- **ViewState serialization** - Not needed; state is preserved in component fields
## Web Forms Declarative Syntax
```html
<asp:[ComponentName]
[All attributes from original Web Forms control]
[Alphabetically ordered]
[Include runat="server" at the end]
/>
Blazor Syntax
<[ComponentName]
[Supported attributes only]
[Same order as Web Forms section for easy comparison]
/>
Usage Notes
[Practical advice for migration] [Common pitfalls to avoid] [Performance considerations if any]
Examples
Basic Usage
@* Description of what this example shows *@
<[ComponentName] Property="value" OnEvent="Handler" />
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 · 730 lines · 119 tokens per session scan A 19230dea25d7
documentation is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (454 stars, last pushed 4mo ago), licensed MIT. It adds 119 tokens to every session and 5,172 once invoked, about $0.0005 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
lumeo
Use when building or editing a Blazor UI that uses the Lumeo component library (the Lumeo NuGet package and its satellites Lumeo.Charts / Lumeo.DataGrid / Lumeo.Editor / Lumeo.Scheduler / Lumeo.Gantt / Lumeo.Motion / Lumeo.Flow), or when the user mentions Lumeo components (Button, DataGrid, Sheet, Dialog, Tabs…
csharp-dotnet
Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…
mapsui
Use when embedding interactive 2D maps in .NET desktop (WinForms/WPF) or mobile (MAUI) applications — tile layers, vector features, map controls. Mapsui: cross-platform .NET map component library.
signs-of-ai
Detect and remove the tells of AI-generated writing in BOTH English and Spanish, and read back the evidence honestly. Use when the user asks to "de-AI" / "humanize" / "un-slop" a draft, to examine whether text carries the tells (delve, tapestry, "it's not just X, it's Y", "here's the thing", em-dash overuse, an…
vela
Compiler-exact code search over a SCIP index - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Indexes .NET itself: C#, VB, Razor Pages, MVC views and Blazor components, with every Razor reference resolved by the compiler into a saved index, where grep sees only…
qa-tester
Verifies programmer deliveries when a ticket reaches Review. Actually runs the application/tests/endpoints to confirm the change works, sets up missing test tooling when needed, and blocks the ticket if execution is impossible. Posts a PASS/FAIL/BLOCKED report; on FAIL, returns the ticket to Todo.