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/acceptance-testingnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill acceptance-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.00071 | $0.01989 |
| Opus 5 | $0.00036 | $0.00994 |
| Sonnet 5 | $0.00014 | $0.00398 |
| Haiku 4.5 | $0.00007 | $0.00199 |
Grade A, and why
acceptance-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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Acceptance Test Authoring (Playwright)
This skill covers writing end-to-end acceptance tests using Playwright (.NET) to verify migrated Blazor applications work correctly.
Architecture
Test Suites
| Suite | Location | Target App | Env Var |
|---|---|---|---|
| WingtipToys | src/WingtipToys.AcceptanceTests/ |
samples/AfterWingtipToys/ |
WINGTIPTOYS_BASE_URL |
| ContosoUniversity | src/ContosoUniversity.AcceptanceTests/ |
samples/AfterContosoUniversity/ |
CONTOSO_BASE_URL |
| Sample App | samples/AfterBlazorServerSide.Tests/ |
samples/AfterBlazorServerSide/ |
N/A (built inline) |
Shared Infrastructure
Every test suite uses the same pattern:
PlaywrightFixture.cs — Shared browser instance:
public class PlaywrightFixture : IAsyncLifetime
{
public IPlaywright Playwright { get; private set; } = null!;
public IBrowser Browser { get; private set; } = null!;
public async Task InitializeAsync()
{
Playwright = await Microsoft.Playwright.Playwright.CreateAsync();
Browser = await Playwright.Chromium.LaunchAsync(new BrowserTypeLaunchOptions
{
Headless = true
});
}
public async Task DisposeAsync()
{
await Browser.DisposeAsync();
Playwright.Dispose();
}
public async Task<IPage> NewPageAsync()
{
var context = await Browser.NewContextAsync(new BrowserNewContextOptions
{
IgnoreHTTPSErrors = true
});
return await context.NewPageAsync();
}
}
[CollectionDefinition("Playwright")]
public class PlaywrightCollection : ICollectionFixture<PlaywrightFixture> { }
TestConfiguration.cs — Environment-driven base URL:
public static class TestConfiguration
{
public static string BaseUrl =>
Environment.GetEnvironmentVariable("WINGTIPTOYS_BASE_URL")
?? "https://localhost:5001";
}
Writing a New Test
Step 1: Create the Test Class
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 · 262 lines · 71 tokens per session scan A 5fb49c388e7c
acceptance-testing is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 1,989 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
browse
Fast headless browser for QA testing and site dogfooding. (gstack).
e2e-deployment-skill
Use this deployment skill to verify shared skills load during Playwright startup.
launch
Launch Code OSS (VS Code from sources) into an isolated throwaway profile with unique debug ports so you can drive it with @playwright/cli AND attach a Node debugger via dap-cli in the same session. Use when working on VS Code itself and you want to interact with the running workbench, automate chat or UI flows, test…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
actionbook-web-test
Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…