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/l3-performance-optimizationnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill l3-performance-optimizationgit 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.00098 | $0.05703 |
| Opus 5 | $0.00049 | $0.02851 |
| Sonnet 5 | $0.00020 | $0.01141 |
| Haiku 4.5 | $0.00010 | $0.00570 |
Grade A, and why
l3-performance-optimization 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 — 730 lines — stays where its author put it; the contents beside it link to each section on GitHub.
L3: Post-Migration Performance Optimization
⚠️ WARNING: L3 optimization runs AFTER the app builds and works correctly. Do NOT apply L3 changes during initial migration. Use shims first (Session, Response, Request) for functional correctness, then optimize later if needed.
This skill is the optional fourth step in the migration pipeline. It applies after the app builds and runs correctly following L1 (automated), L2 (structural), and L3-architecture (data/identity) passes.
Related skills:
/bwfc-migration— Core markup migration (controls, expressions, layouts)/bwfc-data-migration— EF6 → EF Core, architecture decisions/bwfc-identity-migration— Authentication migration
When to Use This Skill
Apply L3 optimizations when:
- The migrated app builds and runs without errors
- You want measurable performance improvements beyond functional correctness
- You are ready to modernize patterns to .NET 10 idioms
Do NOT run L3 before the app is functional. L3 assumes L1 + L2 + L3-architecture are complete. Applying async patterns to broken code makes debugging harder.
Confidence Levels
Each optimization in this skill is rated:
| Rating | Meaning |
|---|---|
| ✅ Safe | Drop-in change, identical behavior, no review needed |
| ⚠️ Review | Almost always correct, but verify behavior in your specific context |
| 🔴 Risky | Possible semantic difference — review before committing |
Usage Patterns
# Apply all safe optimizations to the whole project
"Run L3 optimization on the migrated ContosoUniversity app"
# Apply a single category
"Apply async/await fixes to Students.razor.cs"
# Report only — no changes
"Generate an L3 optimization report for AfterWingtipToys"
# Ask what's applicable
"What .NET 10 optimizations can we apply to this file?"
1. Async/Await Modernization ✅ Safe
The most impactful change in the L3 pass. Synchronous EF Core calls block the thread pool, hurting throughput under load. Web Forms code-behind often used synchronous DB calls; migrated code preserves that pattern by default.
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 · 730 lines · 98 tokens per session scan A b526eb9b8d38
l3-performance-optimization is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 5,703 once invoked, about $0.0005 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…