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/migration-standardsnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill migration-standardsgit 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/migration-standards)<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/migration-standards"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/migration-standards.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.00079 | $0.07720 |
| Opus 5 | $0.00039 | $0.03860 |
| Sonnet 5 | $0.00016 | $0.01544 |
| Haiku 4.5 | $0.00008 | $0.00772 |
Grade A, and why
migration-standards 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 4d 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 — 646 lines — stays where its author put it; the contents beside it link to each section on GitHub.
⛔ MANDATORY RULES — Read Before Any Migration Work
Data control migration is non-negotiable
- NEVER replace
<asp:ListView>,<asp:FormView>,<asp:GridView>,<asp:DataList>, or<asp:Repeater>with manual HTML,<table>markup, or@foreachloops. - ALWAYS migrate them to the BWFC component of the same name:
<ListView>,<FormView>,<GridView>,<DataList>, and<Repeater>. - These components already exist in the BlazorWebFormsComponents library and are the correct migration target.
- If generated BWFC markup does not compile, fix the markup so the BWFC component works — do not replace the component with hand-written HTML.
-
ALL migrated pages inherit WebFormsPageBase via
@inherits BlazorWebFormsComponents.WebFormsPageBasein_Imports.razor. This gives every page: Session, Response, Request, Server, Cache, ClientScript, ViewState, IsPostBack. -
PRESERVE the original Web Forms API calls. If the Web Forms code says
Session["CartId"], the Blazor code saysSession["CartId"]. If it saysResponse.Redirect("ShoppingCart.aspx"), the Blazor code saysResponse.Redirect("ShoppingCart"). The shims handle the translation. -
NEVER inject raw ASP.NET Core services when a shim exists:
- ❌
[Inject] IHttpContextAccessor→ ✅ UseRequest,Response,Sessionproperties - ❌
[Inject] NavigationManager(for redirects) → ✅ UseResponse.Redirect() - ❌
[Inject] IMemoryCache→ ✅ UseCacheproperty - ❌
HttpContext.Session["key"]→ ✅ UseSession["key"]
- ❌
-
NEVER create Minimal API endpoints to replace Web Forms page actions. If it was a page in Web Forms, it's a page in Blazor.
-
NEVER use cookies to replace Session. If the original code used Session, use SessionShim.
-
AddBlazorWebFormsComponents()in Program.cs registers ALL shims automatically.
Context
When migrating an ASP.NET Web Forms application to Blazor using BlazorWebFormsComponents, these standards define the canonical target architecture, tooling choices, and migration patterns. Established through five WingtipToys migration benchmark runs and codified as a directive by Jeffrey T. Fritz.
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.
- 4d ago First seen · 646 lines · 79 tokens per session scan A c4a1f12e4874
migration-standards is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 7,720 once invoked, about $0.0004 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
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…
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…
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…
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.