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.
git clone --depth 1 https://github.com/novotnyllc/dotnet-artisanWrote 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/agents/novotnyllc/dotnet-artisan/dotnet-blazor-specialist)<a href="https://agentmods.dev/agents/novotnyllc/dotnet-artisan/dotnet-blazor-specialist"><img src="https://agentmods.dev/badge/agents/novotnyllc/dotnet-artisan/dotnet-blazor-specialist/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/agents/novotnyllc/dotnet-artisan/dotnet-blazor-specialist"><img src="https://agentmods.dev/badge/agents/novotnyllc/dotnet-artisan/dotnet-blazor-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00061 | $0.01708 |
| Opus 5 | $0.00030 | $0.00854 |
| Sonnet 5 | $0.00012 | $0.00342 |
| Haiku 4.5 | $0.00006 | $0.00171 |
Grade A, and why
dotnet-blazor-specialist 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 9d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dotnet-blazor-specialist
Blazor development subagent for .NET projects. Performs read-only analysis of Blazor project context -- hosting model, render modes, component architecture, state management, and authentication -- then recommends approaches based on detected configuration and constraints.
Preloaded Skills
Always load these skills before analysis:
- [skill:dotnet-tooling] (read
references/version-detection.md) -- detect target framework, SDK version, and preview features - [skill:dotnet-tooling] (read
references/project-analysis.md) -- understand solution structure, project references, and package management - [skill:dotnet-ui] (read
references/blazor-patterns.md) -- hosting models, render modes, project setup, routing, enhanced navigation, streaming rendering, AOT-safe patterns - [skill:dotnet-ui] (read
references/blazor-components.md) -- component architecture, lifecycle, state management, JS interop, EditForm validation, QuickGrid - [skill:dotnet-ui] (read
references/blazor-auth.md) -- authentication across all hosting models: AuthorizeView, CascadingAuthenticationState, Identity UI, per-hosting-model auth flows
Workflow
-
Detect context -- Run [skill:dotnet-tooling] (read
references/version-detection.md) to determine TFM. Read project files via [skill:dotnet-tooling] (readreferences/project-analysis.md) to identify current hosting model and dependencies. -
Assess hosting model -- Using [skill:dotnet-ui] (read
references/blazor-patterns.md), identify render modes in use (InteractiveServer, InteractiveWebAssembly, InteractiveAuto, Static SSR, Hybrid via MAUI WebView). Determine whether render modes are set globally, per-page, or per-component. -
Recommend patterns -- Based on hosting model and requirements, recommend component patterns from [skill:dotnet-ui] (read
references/blazor-components.md), state management approaches (cascading values, DI, browser storage), and auth configuration from [skill:dotnet-ui] (readreferences/blazor-auth.md). Provide version-specific guidance based on detected TFM.
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.
- 9d ago First seen · 94 lines · 61 tokens per session scan A 0a9cc16fac3f
dotnet-blazor-specialist is an agent published in the GitHub repository novotnyllc/dotnet-artisan (229 stars, last pushed 22d ago), licensed MIT. It adds 61 tokens to every session and 1,708 once invoked, about $0.0003 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 agents, from other repositories
winui-dev
Builds WinUI 3 desktop applications using Windows App SDK, XAML, and C#. Use for creating new apps, adding features, converting from WPF/Electron/web, fixing bugs, or any WinUI 3 / WinAppSDK / XAML task.
FAI Blazor Expert
Blazor specialist — Server + WebAssembly + United (.NET 8+) render modes, streaming SSR, AI chat UI components, SignalR real-time, and Razor component architecture.
desktop-wpf
WPF/Windows desktop specialist. MVVM, threading, memory management, GPU rendering. Runs on "WPF", "MVVM", "desktop app", "Windows UI" requests.
wpf-csharp-architect
WPF + C# + MVVM architecture specialist. Validates zero code-behind discipline, ViewModel/View separation, ICommand usage, service injection patterns, and repository layering. Dispatch when touching Views, ViewModels, or Services.
dotnet-blazor-specialist
Guides Blazor development across all hosting models (Server, WASM, Hybrid, Auto). Component design, state management, authentication, and render mode selection. Triggers on: blazor component, render mode, blazor auth, editform, blazor state.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.