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/nevaberry/nevaberry-plugins/aspnet-core-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill aspnet-core-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/aspnet-core-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/aspnet-core-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/aspnet-core-knowledge-patch.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.00011 | $0.01891 |
| Opus 5 | $0.00005 | $0.00945 |
| Sonnet 5 | $0.00002 | $0.00378 |
| Haiku 4.5 | $0.00001 | $0.00189 |
Grade A, and why
aspnet-core-knowledge-patch 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 3d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ASP.NET Core Knowledge Patch
Use this patch when implementing, reviewing, testing, or upgrading ASP.NET Core applications. Check breaking behavior first, then open only the topic references relevant to the task.
Index
| Reference | Topics |
|---|---|
| Components, Navigation, and Interop | Blazor navigation, reconnection, JavaScript interop, streaming, component state, circuits, and culture |
| Forms, Validation, and Persistence | Recursive validation, form binding, and persistent component state |
| Hosting, HTTP, Caching, and Security | Kestrel, HTTP.sys, memory pools, and development domains |
| Migrations, Assets, and Tooling | Blazor WebAssembly migration, boot assets, fingerprinting, bundlers, and testing |
| Observability, Identity, and SignalR | Exception diagnostics, authentication and Identity metrics, passkeys, and Identity redirects |
| OpenAPI, Minimal APIs, and JSON | OpenAPI 3.1, OpenAPI.NET 2, transformers, XML comments, and JSON converters |
Breaking-change checks
Stop depending on blazor.boot.json
The boot configuration is inlined into dotnet.js; there is no separate
blazor.boot.json. Workflows that inspect or mutate the old file, including
published-integrity and DLL-extension customizations, have no documented direct
replacement. Remove assumptions about that artifact before upgrading.
Also remove BlazorCacheBootResources. Fingerprinted browser assets now provide
the cache behavior, so the property is unavailable or ineffective.
Audit WebAssembly response-stream consumers
Blazor WebAssembly enables response streaming by default. ReadAsStreamAsync
returns BrowserHttpReadStream, which does not support synchronous reads. Code
that expects a buffered MemoryStream must become asynchronous or disable
streaming per request:
What ships with it
7 files 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.
- coverage.json 1.2 KB
- references/components-navigation-and-interop.md 3.3 KB
- references/forms-validation-and-persistence.md 1.8 KB
- references/hosting-http-caching-and-security.md 1.2 KB
- references/migrations-assets-and-tooling.md 2.6 KB
- references/observability-identity-and-signalr.md 2.0 KB
- references/openapi-minimal-apis-and-json.md 2.3 KB
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.
- 3d ago First seen · 241 lines · 11 tokens per session scan A bb0bc22e374e
aspnet-core-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 1,891 once invoked, about $0.0001 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
dotnet-analyzers
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA). Use when fixing unnecessary usings, code style violations, analyzer warnings, or verifying format compliance.
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
dotnet-dependency
This skill should be used when investigating .NET project dependencies, understanding why packages are included, listing references, or auditing for outdated/vulnerable packages.
dotnet-inspect
Query .NET APIs across NuGet packages, platform libraries, and local files. Search for types, list API surfaces, compare and diff versions, find extension methods and implementors. Use whenever you need to answer questions about .NET library contents.
dotnet-run-file
Run script-like CSharp programs using dotnet run file.cs. Use this skill when users want to execute CSharp code directly, write one-liner scripts via stdin, or learn about run file directives.
dotnet-verify
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept…