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/bwfc-identity-migrationnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill bwfc-identity-migrationgit 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/bwfc-identity-migration)<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/bwfc-identity-migration"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/bwfc-identity-migration.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.1 | $0.00122 | $0.04421 |
| Opus 5 | $0.00061 | $0.02210 |
| Sonnet 5 | $0.00024 | $0.00884 |
| Haiku 4.5 | $0.00012 | $0.00442 |
Grade A, and why
bwfc-identity-migration 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 6d 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Forms Identity → Blazor Identity Migration
Overview
| Web Forms Auth System | Era | Blazor Migration Path |
|---|---|---|
| ASP.NET Identity (OWIN) | 2013+ | ASP.NET Core Identity (closest match) |
| ASP.NET Membership | 2005-2013 | Core Identity (schema migration required) |
| FormsAuthentication | 2002-2005 | Core Identity or cookie auth |
Related: /bwfc-migration (markup), /bwfc-data-migration (EF/architecture)
Critical Rules
- Cookie auth requires HTTP endpoints — login/register/logout MUST use
<form method="post">+ minimal API endpoints. Component event handlers (@onclick) silently fail for cookie operations in interactive mode. - NEVER replace LoginView with AuthorizeView — BWFC
LoginViewusesAuthenticationStateProvidernatively with same template names (AnonymousTemplate,LoggedInTemplate). - DisableAntiforgery required — Blazor forms don't include antiforgery tokens. All auth endpoints must call
.DisableAntiforgery(). - Session-based auth data works —
Session["key"]viaWebFormsPageBase.Session/SessionShim. Don't injectIHttpContextAccessor.
Quick Reference
BWFC Login Controls (drop-in replacements)
<Login />, <LoginName />, <LoginStatus />, <LoginView>, <CreateUserWizard />, <ChangePassword />, <PasswordRecovery />
Auth Endpoint Pattern
// Program.cs — login via HTTP POST (required for cookie auth)
app.MapPost("/Account/LoginHandler", async (HttpContext ctx, SignInManager<IdentityUser> sm) =>
{
var form = await ctx.Request.ReadFormAsync();
var result = await sm.PasswordSignInAsync(form["email"]!, form["password"]!, false, false);
return result.Succeeded ? Results.Redirect("/") : Results.Redirect("/Account/Login?error=failed");
}).DisableAntiforgery();
Companion Documents
| Document | Content |
|---|---|
| IDENTITY-PATTERNS.md | Cookie auth details, identity config steps, BWFC login controls, authorization patterns, endpoint templates, OWIN mapping, gotchas |
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.
- 6d ago First seen · 504 lines · 122 tokens per session scan A adca366f8f1a
bwfc-identity-migration is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 4,421 once invoked, about $0.0006 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…
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…
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.
dotnet-eslint
Use ESLint in .NET repositories that ship JavaScript, TypeScript, React, or other Node-based frontend assets. Use when a repo needs a configurable CLI lint gate for frontend correctness, import hygiene, unsafe patterns, or framework-specific rules.
dotnet-vuln-scanner
.NET 组件漏洞扫描 skill。覆盖 NuGet 包、DLL 引用、配置文件中的依赖版本与 CVE/GHSA 触发条件。输出组件漏洞清单、可利用性评估和修复版本建议。.
dotnet-sonarjs
Use SonarJS-derived rules in .NET repositories that ship JavaScript or TypeScript frontends and need deeper bug-risk, code-smell, or cognitive-complexity checks than a minimal ESLint baseline. Use when the repo wants eslint-plugin-sonarjs locally or already runs SonarQube or SonarCloud in CI.