Borrowing it
Nothing to install: this file belongs to vchelaru/XnaFiddle. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vchelaru/XnaFiddle/main/.claude/skills/e2e-testing/SKILL.mdgit clone --depth 1 https://github.com/vchelaru/XnaFiddleWrote 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/vchelaru/xnafiddle/e2e-testing)<a href="https://agentmods.dev/skills/vchelaru/xnafiddle/e2e-testing"><img src="https://agentmods.dev/badge/skills/vchelaru/xnafiddle/e2e-testing.svg" alt="Measured on agentmods" height="20"></a>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.00096 | $0.02167 |
| Opus 5 | $0.00048 | $0.01084 |
| Sonnet 5 | $0.00019 | $0.00433 |
| Haiku 4.5 | $0.00010 | $0.00217 |
Grade A, and why
e2e-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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
E2E Testing
Test project: XnaFiddle.E2E.Tests (NUnit + Microsoft.Playwright.NUnit). Nullable is enabled here (unlike BlazorGL/Core — don't copy their nullable-off assumptions). dotnet test auto-discovers every [Test], so adding a test needs no CI edit. Runtime domain facts (leaks, lifecycle, UseReferenceDevice) live in the game-lifecycle skill; this skill is only about authoring tests.
The harness flow
dotnet publish XnaFiddle.BlazorGL -c Release -o <dir>produces the standalone WASM app.PublishOutput.ResolveWebRoot()finds the served web root: honors env varE2E_PUBLISH_DIR, else falls back to<repoRoot>/artifacts/e2e-publish. Accepts either the publish root (has awwwroot) or thewwwrootitself; throws if noindex.html.StaticSiteHost.StartAsync(webRoot)serves it in-process via Kestrel on an OS-assigned port (http://127.0.0.1:0). UsesUseBlazorFrameworkFilesso_frameworkWebcil assemblies getapplication/wasm(a plain static server serves octet-stream, which the browser refuses).MapFallbackToFile("index.html")for deep links.- Playwright drives headless Chromium against
host.BaseUrl.
E2ETestBase (base fixture) owns the expensive shared pieces in OneTimeSetUp: the Kestrel host, Playwright, the browser, and one IBrowserContext. Each [Test] gets a fresh IPage ([SetUp]/[TearDown]) so a still-running game, a set window._canvasContextType, or leftover DOM can't leak across tests. The context is shared (not per-test) so the ~15-20 MB WASM payload stays in the HTTP cache between pages instead of re-downloading each test. SmokeTest and CoreBehaviorsTest both extend it; put shared helpers (BootAsync, ClickRunAsync, WaitForWebGlContextAsync, SetEditorValueAsync, etc.) on the base.
Locally: if artifacts/e2e-publish/wwwroot/index.html already exists, skip publish — just dotnet test. But if you changed app code (a new data-testid, a hook), re-publish first or the served app is stale and tests fail on the missing hook. CI (.github/workflows/e2e.yml) does publish → build test proj → playwright.ps1 install chromium → dotnet test --no-build. Full suite (14 tests, no shader test) runs ~1.5 min locally with warm caches.
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.
- yesterday First seen · 85 lines · 96 tokens per session scan A 1b467c235362
e2e-testing is a skill published in the GitHub repository vchelaru/XnaFiddle (13 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 2,167 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-09-04.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
trailblaze
Use when working with Trailblaze — natural-language device control for coding agents across iOS, Android, and web, with replayable .trail.yaml files as the artifact. Trigger on mentions of Trailblaze, the trailblaze CLI, .trail.yaml files, trailmaps, waypoints, or requests to drive / author / debug / run UI tests on…
Detox Mobile Testing
Gray-box end-to-end testing for React Native apps with Detox. Covers .detoxrc.js configuration, build and test commands, matchers, device.launchApp control, automatic synchronization, and macOS CI pipelines.