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/cli-transform-authoringnpx skills add FritzAndFriends/BlazorWebFormsComponents --skill cli-transform-authoringgit 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.00082 | $0.01719 |
| Opus 5 | $0.00041 | $0.00860 |
| Sonnet 5 | $0.00016 | $0.00344 |
| Haiku 4.5 | $0.00008 | $0.00172 |
Grade A, and why
cli-transform-authoring 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Transform Authoring
This skill covers creating new transforms for the webforms-to-blazor CLI migration pipeline.
Architecture Overview
The migration CLI uses two transform interfaces that run in sequence during file conversion:
- Markup transforms (
IMarkupTransform) — Convert.aspx/.ascx/.mastermarkup to.razorsyntax - Code-behind transforms (
ICodeBehindTransform) — Convert.aspx.cscode-behind to.razor.cs
Both interfaces share the same contract:
public interface IMarkupTransform // (or ICodeBehindTransform)
{
string Name { get; }
int Order { get; }
string Apply(string content, FileMetadata metadata);
}
Name— Human-readable identifier (used in logs and diagnostics)Order— Execution sequence (ascending). Lower numbers run first.Apply— Takes current content + file metadata, returns transformed content
Pipeline Execution Order
MigrationPipeline runs transforms in this order:
- Markup transforms (sorted by
Orderascending) — all run on.razorcontent - Code-behind transforms (sorted by
Orderascending) — all run on.razor.cscontent - Semantic patterns (
SemanticPatternCatalog) — page-level rewrites after all transforms
FileMetadata
Every transform receives FileMetadata which carries context about the file being processed:
OriginalPath— Source.aspxpathOutputPath— Target.razorpathPageDirectives— Parsed directive info (CodeBehind, Inherits, MasterPageFile)MarkupContent— Can be set by code-behind transforms to modify the markup fileCodeBehindContent— The code-behind sourceIsUserControl/IsMasterPage— File type flags
Creating a New Transform
Step 1: Create the Transform Class
src/BlazorWebFormsComponents.Cli/Transforms/Markup/MyNewTransform.cs
— or —
src/BlazorWebFormsComponents.Cli/Transforms/CodeBehind/MyNewTransform.cs
using BlazorWebFormsComponents.Cli.Pipeline;
namespace BlazorWebFormsComponents.Cli.Transforms.Markup; // or .CodeBehind
public class MyNewTransform : IMarkupTransform // or ICodeBehindTransform
{
public string Name => "MyNewTransform";
public int Order => 500; // Choose based on dependencies
public string Apply(string content, FileMetadata metadata)
{
// Return content unchanged if this transform doesn't apply
if (!content.Contains("pattern-to-match"))
return content;
// Apply transformation
return content.Replace("old-pattern", "new-pattern");
}
}
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 · 200 lines · 82 tokens per session scan A c863f717d6af
cli-transform-authoring is a skill published in the GitHub repository FritzAndFriends/BlazorWebFormsComponents (449 stars, last pushed 2mo ago), licensed MIT. It adds 82 tokens to every session and 1,719 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…
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…
vela
Compiler-exact code search for .NET solutions - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Covers C#, VB, Razor Pages, MVC views and Blazor components, which grep and every other code-intelligence tool miss. Deterministic, built on Roslyn, never modifies the…
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.