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/wingtip-migration-testnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill wingtip-migration-testgit 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/wingtip-migration-test)<a href="https://agentmods.dev/skills/fritzandfriends/blazorwebformscomponents/wingtip-migration-test"><img src="https://agentmods.dev/badge/skills/fritzandfriends/blazorwebformscomponents/wingtip-migration-test.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 | $0.00136 | $0.02456 |
| Opus 5 | $0.00068 | $0.01228 |
| Sonnet 5 | $0.00027 | $0.00491 |
| Haiku 4.5 | $0.00014 | $0.00246 |
Grade A, and why
wingtip-migration-test 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 4d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WingtipToys Migration Test
End-to-end migration benchmark for the canonical WingtipToys Web Forms sample. This workflow uses the repository's migration toolkit as the public entry point, preserves the migrated application shape in samples\AfterWingtipToys\, and considers the run successful only when the existing Playwright acceptance tests pass.
Benchmark Integrity Rules
This workflow is a benchmark, so every run must start from scratch.
Required behavior
- Start with the raw Web Forms source in
samples\WingtipToys\. - Clear
samples\AfterWingtipToys\before each run. - Run
migration-toolkit\scripts\bwfc-migrate.ps1to produce the output for this run. - Repair only the fresh output produced during the current run.
Forbidden behavior
- Do not restore or copy previously migrated content into
samples\AfterWingtipToys\. - Do not use git history as migration input or repair content:
- no
git restore - no
git checkout - no
git showto pull old file contents into the run - no copying files from prior commits, branches, tags, or stashes
- no
- Do not reuse prior benchmark outputs from:
samples\AfterWingtipToys\dev-docs\migration-tests\wingtiptoys\run*- session artifacts, temp folders, or prior migration snapshots
- Do not treat an earlier repaired sample as the answer. The point of the run is to measure what the toolkit plus current repair work can achieve from scratch.
If a run uses prior migrated content or git-sourced repairs, the benchmark is invalid and must be restarted from a freshly cleared output folder.
Paths
| Item | Path |
|---|---|
| Web Forms wrapper | samples/WingtipToys/ |
| Effective Web Forms app | samples/WingtipToys/WingtipToys/ |
| Blazor output | samples/AfterWingtipToys/ |
| Toolkit entry point | migration-toolkit/scripts/bwfc-migrate.ps1 |
| Toolkit skills | migration-toolkit/skills/ |
| Acceptance tests | src/WingtipToys.AcceptanceTests/ |
| Run reports | dev-docs/migration-tests/wingtiptoys/ |
| Report template | ./REPORT-TEMPLATE.md |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 251 lines · 136 tokens per session scan A bde471c92bab
wingtip-migration-test is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 136 tokens to every session and 2,456 once invoked, about $0.0007 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
release-gatekeeper
End-to-end release validation for Connapse — the 'final boss' before any version ships. Downloads the latest alpha from GitHub Releases, deploys an isolated Docker instance (separate from production), then systematically tests every feature: UI via Playwright, API via curl/REST, MCP tools, search quality, security…
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…
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.
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.
qa-tester
Verifies programmer deliveries when a ticket reaches Review. Actually runs the application/tests/endpoints to confirm the change works, sets up missing test tooling when needed, and blocks the ticket if execution is impossible. Posts a PASS/FAIL/BLOCKED report; on FAIL, returns the ticket to Todo.