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/fritzandfriends/blazorwebformscomponents/cli-compile-surface-hardeningnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill cli-compile-surface-hardeninggit 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/cli-compile-surface-hardening)<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/cli-compile-surface-hardening"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/cli-compile-surface-hardening.svg" alt="Measured on agentmods" 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 | $0.00025 | $0.00532 |
| Opus 5 | $0.00013 | $0.00266 |
| Sonnet 5 | $0.00005 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
cli-compile-surface-hardening 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 5d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Use this when the migration CLI starts emitting more generated .razor.cs files or copying more legacy source into the output project. The goal is to preserve deterministic L1 behavior while preventing compile failures from style analyzers, generic Razor component inference, or unresolved markup references.
Patterns
- In generated migration projects, prefer
<EnforceCodeStyleInBuild>false</EnforceCodeStyleInBuild>over broad warning suppression when copied legacy files would otherwise fail repo-level IDE analyzers. - Add validator generic arguments with the BWFC component's actual generic parameter name, not an assumed
TValuealias:RequiredFieldValidator→Type="string"CompareValidator/RangeValidator→InputType="string"
- Run markup-driven member stub generation after the main code-behind transforms, using transformed Razor markup (
metadata.MarkupContent) as the source of truth. - Stub only the deterministic missing-member shapes that are safe to infer mechanically:
@MethodName()→ render-method stub returningobject?@_fieldName→ privateobject?fieldOnClick="@HandlerName"and similar →void HandlerName(object? sender, EventArgs e)
- Register new transforms in both production DI (
src\BlazorWebFormsComponents.Cli\Program.cs) andtests\BlazorWebFormsComponents.Cli.Tests\TestHelpers.csso the lightweight and full pipelines stay aligned.
Examples
src\BlazorWebFormsComponents.Cli\Transforms\Markup\ValidatorGenericTypeTransform.cssrc\BlazorWebFormsComponents.Cli\Transforms\CodeBehind\MarkupReferencedMemberStubTransform.cstests\BlazorWebFormsComponents.Cli.Tests\TransformUnit\CompiledCodeBehindStubPipelineTests.cs
Anti-Patterns
- Suppressing all warnings/errors in the generated project when only code-style analyzers are the problem.
- Injecting
TValue="string"into BWFC validators that actually exposeTypeorInputTypegeneric parameters. - Generating markup-reference stubs before markup transforms run, or reading original Web Forms markup instead of the transformed Razor output.
- Emitting placeholder stubs for every
@Identifiertoken; restrict deterministic generation to the specific reference shapes you can classify safely.
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.
- 5d ago First seen · 34 lines · 25 tokens per session scan A ba45293fcfdd
cli-compile-surface-hardening is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 532 once invoked, about $0.0001 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
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), or when the user mentions Lumeo components (Button, DataGrid, Sheet, Dialog, Tabs, DatePicker, Toast…
sync-repos
Synchronize external repositories used by PKMDS-Blazor. Use when asked to sync, get latest, refresh related repos, inspect upstream changes, or prepare work that depends on current PKHeX, PokeAPI, Pokemon Showdown, sprites, or plugin sources.
address-pr-feedback
Address unresolved GitHub pull request review feedback in PKMDS-Blazor. Use when asked to handle PR comments, review threads, requested changes, or reviewer follow-up.
implement-issue
Implement a PKMDS-Blazor GitHub issue end to end. Use when asked to investigate and implement an issue, bug, feature request, or feature-parity item and prepare it for review.
blazorbindings-maui-third-party
Integrate third-party .NET MAUI control libraries into BlazorBindings.Maui apps by generating Razor wrappers, registering attached properties, and bridging to native elements for imperative APIs such as popups or bottom sheets. Use when adding, updating, or troubleshooting a MAUI control package in a…
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…