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 skills add StefanTheCode/dotnet-ai-toolkit --skill crud-vs-event-sourcinggit clone --depth 1 https://github.com/StefanTheCode/dotnet-ai-toolkitWrote 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/stefanthecode/dotnet-ai-toolkit/crud-vs-event-sourcing)<a href="https://agentmods.dev/skills/stefanthecode/dotnet-ai-toolkit/crud-vs-event-sourcing"><img src="https://agentmods.dev/badge/skills/stefanthecode/dotnet-ai-toolkit/crud-vs-event-sourcing.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00161 | $0.02116 |
| Opus 5 | $0.00081 | $0.01058 |
| Sonnet 5 | $0.00032 | $0.00423 |
| Haiku 4.5 | $0.00016 | $0.00212 |
Grade A, and why
crud-vs-event-sourcing 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRUD vs Event Sourcing
Given a description of a domain, aggregate, or feature, decide the right persistence and architecture style — CRUD, Event Sourcing (ES), or event-driven-but-still-CRUD — and return a concrete, defensible recommendation with a .NET implementation sketch.
The default answer is CRUD. Event Sourcing must earn its place. This skill exists to stop teams from either (a) reaching for ES because it's fashionable, or (b) staying in CRUD when the domain genuinely needs history and behavior.
When this runs
The user describes a feature/aggregate ("an Order", "a bank Account", "a user Profile", "a shopping Cart", "a support Ticket") and asks whether it should be CRUD or event-sourced — or shares an existing CRUD model and asks if it should change. If the description is too thin to score, ask only for what's missing from the scoring inputs below; otherwise proceed.
Clarify these three separations up front, because they are constantly conflated:
- CRUD vs Event Sourcing is a persistence / state-modeling choice (store current state vs store the stream of events and fold them into state).
- Event-driven architecture is an integration choice (components communicate via events/messages). You can be fully event-driven while every service internally uses CRUD.
- CQRS (separate read and write models) often pairs with ES but is independent of it. ES almost always implies CQRS; CQRS does not require ES.
Name which of these the user is actually asking about before recommending anything.
Workflow
- Restate the aggregate and its job in one sentence, so the user can correct a wrong assumption early.
- Gather the scoring inputs (below). If ≥2 are unknown and can't be inferred, ask for those specific ones — nothing else.
- Score each of the 8 signals as favoring CRUD (0), neutral (1), or favoring ES (2). Show the table.
- Read the total against the bands, but override the number when a single hard signal dominates (e.g. a legal, immutable, per-change audit requirement pushes to ES regardless of the sum; a simple lookup/reference table stays CRUD regardless).
- Recommend one of: CRUD, CRUD + domain events for integration, ES for this one aggregate (rest CRUD), or full ES + CQRS. Recommending ES for the whole system is almost always wrong — flag it if the user implies that.
- Give the .NET implementation sketch for the recommendation (see reference file).
- State the cost honestly — what ES will make harder (querying, tooling, onboarding, GDPR deletes, schema/versioning of events).
What ships with it
2 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.
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.
- 8d ago First seen · 117 lines · 161 tokens per session scan A 14d9bdb1eb06
crud-vs-event-sourcing is a skill published in the GitHub repository StefanTheCode/dotnet-ai-toolkit (19 stars, last pushed 29d ago), licensed MIT. It adds 161 tokens to every session and 2,116 once invoked, about $0.0008 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-core
.NET and C# implementation guidance — stack-specific. Covers application patterns, infrastructure, observability, testing, security, and API design for .NET 8/9 applications. Use when the user asks how to implement something in .NET, whether C# code is idiomatic, MediatR/EF Core patterns, .NET testing, observability…
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
azure-maps-search-dotnet
Azure Maps SDK for .NET. Location-based services including geocoding, routing, rendering, geolocation, and weather. Use for address search, directions, map tiles, IP geolocation, and weather data. Triggers: "Azure Maps", "MapsSearchClient", "MapsRoutingClient", "MapsRenderingClient", "geocoding .NET", "route…
azure-eventgrid-dotnet
Azure Event Grid SDK for .NET. Client library for publishing and consuming events with Azure Event Grid. Use for event-driven architectures, pub/sub messaging, CloudEvents, and EventGridEvents. Triggers: "Event Grid", "EventGridPublisherClient", "CloudEvent", "EventGridEvent", "publish events .NET", "event-driven"…
azure-mgmt-apicenter-dotnet
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…
minimal-api-file-upload
File upload endpoints in ASP.NET minimal APIs (.NET 8+).