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/bunit-testingnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill bunit-testinggit 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.00086 | $0.02787 |
| Opus 5 | $0.00043 | $0.01393 |
| Sonnet 5 | $0.00017 | $0.00557 |
| Haiku 4.5 | $0.00009 | $0.00279 |
Grade A, and why
bunit-testing 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bUnit Test Authoring
This skill covers writing new bUnit v2 component tests for the BlazorWebFormsComponents library.
Not for migration. If you need to migrate existing tests from bUnit beta to v2, use the
bunit-test-migrationskill instead.
Test Infrastructure
BlazorWebFormsTestContext
All BWFC component tests should inherit from BlazorWebFormsTestContext, which extends bUnit's BunitContext with pre-registered services:
public abstract class BlazorWebFormsTestContext : BunitContext
{
// Pre-configured:
// - JSInterop.Mode = JSRuntimeMode.Loose
// - LinkGenerator (mocked)
// - IHttpContextAccessor (mocked)
// - IWebHostEnvironment (mocked with temp paths)
// - IMemoryCache
// - CacheShim, ServerShim, ClientScriptShim
// - ILogger<T> (with optional xUnit output)
}
This base class ensures components that depend on WebFormsPageBase shims can render without additional setup.
Test File Location
Tests are .razor files organized by component name:
src/BlazorWebFormsComponents.Test/
├── Button/
│ ├── Click.razor
│ ├── Enabled.razor
│ └── Style.razor
├── GridView/
│ ├── Selection.razor
│ ├── Sorting.razor
│ └── Paging.razor
├── Validations/
│ └── SetFocusOnErrorTests.razor
└── ...
Test Naming Convention
ComponentName_Scenario_ExpectedBehavior
Examples:
Button_Click_InvokesHandlerGridView_WithDataSource_RendersRowsRequiredFieldValidator_BlankInput_DisplaysError
Writing Tests
Basic Pattern
@inherits BlazorWebFormsTestContext
@code {
[Fact]
public void Button_Click_InvokesHandler()
{
// Arrange
var clicked = false;
var cut = Render(@<Button OnClick="() => clicked = true">Submit</Button>);
// Act
cut.Find("input").Click();
// Assert
clicked.ShouldBeTrue();
}
}
Testing Component Properties
@code {
[Fact]
public void Label_Text_RendersInSpan()
{
var cut = Render(@<Label Text="Hello World" />);
cut.Find("span").TextContent.ShouldBe("Hello World");
}
[Fact]
public void TextBox_Visible_False_RendersNothing()
{
var cut = Render(@<TextBox Visible="false" />);
cut.FindAll("input").Count.ShouldBe(0);
}
}
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 · 424 lines · 86 tokens per session scan A 092e1a9f8d76
bunit-testing is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 2,787 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
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…
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.
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.
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…