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 instructions/fritzandfriends/blazorwebformscomponents/copilot-instructionsgit 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.06332 | $0.06332 |
| Opus 5 | $0.03166 | $0.03166 |
| Sonnet 5 | $0.01266 | $0.01266 |
| Haiku 4.5 | $0.00633 | $0.00633 |
Grade A, and why
BlazorWebFormsComponents copilot-instructions.md 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 — 606 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions for BlazorWebFormsComponents
Project Overview
BlazorWebFormsComponents is a library that provides Blazor components emulating ASP.NET Web Forms controls, enabling migration from Web Forms to Blazor with minimal markup changes. The project helps developers reuse their existing Web Forms markup in Blazor applications.
Core Requirements
ASP.NET Web Forms components that ship with .NET Framework 4.8 should be recreated as Blazor Components with:
-
Same Name - The Blazor component must have the identical name as the original Web Forms control (e.g.,
<asp:Button>becomes<Button>,<asp:GridView>becomes<GridView>) -
Same Attributes and Properties - Support the same attribute names and property signatures as the original control wherever possible. This enables developers to migrate markup with minimal changes (removing only
asp:prefix andrunat="server") -
Identical HTML Output - The rendered HTML must match what the original Web Forms control produces. This ensures:
- Existing CSS styles continue to work
- JavaScript that targets the HTML structure remains functional
- Visual appearance is preserved after migration
What This Means in Practice
<!-- Original Web Forms -->
<asp:Button ID="btnSubmit" Text="Submit" CssClass="btn-primary" OnClick="Submit_Click" runat="server" />
<!-- Blazor Equivalent (should render identical HTML) -->
<Button Text="Submit" CssClass="btn-primary" OnClick="Submit_Click" />
Both should render:
<button type="submit" class="btn-primary">Submit</button>
Reference Documentation
- Original Web Forms controls: https://docs.microsoft.com/en-us/dotnet/api/system.web.ui.webcontrols?view=netframework-4.8
- Use the .NET Framework 4.8 reference source to verify HTML output patterns
Technology Stack
- .NET Version: .NET 10.0 (see
global.jsonfor SDK version) - Framework: Blazor (migration target is .NET 10 static SSR; samples also include Server-Side and WebAssembly)
- Project Type: Razor Class Library (
Microsoft.NET.Sdk.Razor) - Testing Framework: xUnit with bUnit for Blazor component testing
- Assertion Library: Shouldly
- Mocking: Moq
- Build/Versioning: Nerdbank.GitVersioning
- CSS Utilities: BlazorComponentUtilities
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 · 606 lines · 6,332 tokens per session scan A bbd30f8bb019
BlazorWebFormsComponents copilot-instructions.md is an instructions file published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 6,332 tokens to every session, about $0.0317 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 instructions, from other repositories
PKMDS-Blazor AGENTS.md
AGENTS.md instructions for codemonkey85/PKMDS-Blazor, covering agents.md, quick commands, architecture overview, project layout and build and ci/cd (github actions).
Lumeo CLAUDE.md
Instructions for Brain2k-0005/Lumeo, covering lumeo — project rules, rule #1: no assistant branding in commits, architecture, build commands and coding conventions.
FamilyNido CLAUDE.md
Instructions for pablitofernandez/FamilyNido, covering claude.md, c# development section start, c# instructions, general instructions and naming conventions.
vela-skill AGENTS.md
Instructions for dbhq-uk/vela-skill, covering agents.md, what this is, layout, the three constraints that define this tool and why razor works here and nowhere else.
PKMDS-Blazor copilot-instructions.md
Copilot instructions for codemonkey85/PKMDS-Blazor: See AGENTS.md at the repository root for full agent instructions, including build commands, project layout, and PKHeX.Core guidance.
PKMDS-Blazor CLAUDE.md
Claude Code instructions for codemonkey85/PKMDS-Blazor, a project described as: PKMDS: Pokémon Save Editor for Web (no support for game hacks).