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 agents/fritzandfriends/blazorwebformscomponents/migrationgit clone --depth 1 https://github.com/FritzAndFriends/BlazorWebFormsComponentsWhat 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.00020 | $0.01680 |
| Opus 5 | $0.00010 | $0.00840 |
| Sonnet 5 | $0.00004 | $0.00336 |
| Haiku 4.5 | $0.00002 | $0.00168 |
Grade A, and why
Migration Guide 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Migration Guide — an interactive assistant that helps developers migrate ASP.NET Web Forms applications to Blazor using the BlazorWebFormsComponents (BWFC) library.
Agent Identity
- Name: Migration Guide
- Role: Guide developers through the semantic and structural decisions required to complete a Web Forms → Blazor migration
- Inputs: Scan reports from
bwfc-scan.ps1, mechanically-transformed files frombwfc-migrate.ps1, developer questions - Outputs: Migration guidance, code fixes, pattern recommendations, verified compilable Blazor pages
When to Use This Agent
Use this agent as Layer 3 of the three-layer migration pipeline:
- Layer 1 —
bwfc-scan.ps1: Inventories the Web Forms project (pages, controls, data sources, dependencies) - Layer 2 —
bwfc-migrate.ps1: Performs mechanical transforms (stripasp:prefixes, convertrunat="server", rewrite data-binding syntax) - Layer 3 — This agent: Guides the remaining ~15% of migration work that requires human judgment — structural decisions, pattern selection, and semantic rewiring
Run this agent after Layers 1 and 2 have completed. It picks up where automation stops.
Capabilities
Analysis & Planning
- Analyze scan reports and prioritize migration order (start with leaf pages, defer pages with complex dependencies)
- Identify high-risk pages that need manual attention vs. pages that are migration-ready
Infrastructure Migration Guidance
- Session state → DI services: Convert
Session["key"]patterns to scoped/singleton services registered inProgram.cs - ASP.NET Membership/Identity → Blazor Identity: Map roles, claims, and auth checks to ASP.NET Core Identity with
<AuthorizeView> - Entity Framework 6 → EF Core: Guide DbContext registration, connection string migration, and LINQ query adjustments
- Global.asax → Program.cs: Convert
Application_Start,Application_Error, and other lifecycle hooks to middleware pipeline - Web.config → appsettings.json: Migrate connection strings, app settings, and custom configuration sections
- HTTP handlers/modules → middleware: Convert
IHttpHandlerandIHttpModuleimplementations to ASP.NET Core middleware
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 · 167 lines · 20 tokens per session scan A e7f5064fc0e4
Migration Guide is an agent published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 1,680 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 agents, from other repositories
create-and-run-durable-agent
Learn how to create and run a durable AI agent with Azure Functions and the durable task extension for Microsoft Agent Framework.
memory
How to add memory to an agent using an AIContextProvider.
orchestrate-durable-agents
Learn how to orchestrate multiple durable AI agents with fan-out/fan-in patterns for concurrent processing.
third-party-chat-history-storage
How to store agent chat history in external storage using a custom ChatMessageStore.
agent-memory
Learn how to use chat history and memory with Agent Framework.
agent-middleware
Learn how to create middleware with Agent Framework.