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 skills add FritzAndFriends/BlazorWebFormsComponents --skill bunit-testinggit 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/bunit-testing)<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/bunit-testing"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/bunit-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/bunit-testing"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/bunit-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.02787 |
| Opus 5.5 | $0.00034 | $0.01115 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 424 lines · 86 tokens per session scan A 092e1a9f8d76
bunit-testing is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (454 stars, last pushed 4mo ago), licensed MIT. It adds 86 tokens to every session and 2,787 once invoked, about $0.0003 per session on Opus 5.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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.