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 instructions/cwoodruff/dotnet-claude-code-kit/claude-mdgit clone --depth 1 https://github.com/cwoodruff/dotnet-claude-code-kitWhat 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.00845 | $0.00845 |
| Opus 5 | $0.00423 | $0.00423 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00085 | $0.00085 |
Grade A, and why
dotnet-claude-code-kit CLAUDE.md 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — .NET Solution Guide
Project overview
[SolutionName] is an ASP.NET Core [10] solution: [one-sentence description].
[SolutionName]/
[SolutionName].Api/ # ASP.NET Core Minimal API — endpoints, DI wiring, middleware
[SolutionName].Core/ # Domain entities, interfaces, business rules (no project dependencies)
[SolutionName].Data/ # EF Core DbContext, configurations, migrations (depends on Core only)
[SolutionName].Tests/ # xUnit test project
Dependency direction: Api → Data → Core. Core never references Data or Api.
Build, test, and run
- Build:
dotnet build - Test:
dotnet test --nologo - Run API:
dotnet run --project [SolutionName].Api - Format check:
dotnet format --verify-no-changes - Add a migration: use the
/ef-migrationskill — never hand-edit migration files
Run dotnet build after any multi-file change and fix all warnings, not just errors. Treat analyzer warnings as failures.
Conventions (always apply)
- Target framework:
net10.0. Nullable reference types are enabled; never introduce#nullable disable. - File-scoped namespaces,
varwhen the type is apparent, expression-bodied members only for one-liners. async/awaitall the way down. Never call.Resultor.Wait(). Accept aCancellationTokenin every async public API method and pass it through.- Use
recordtypes for DTOs and request/response models. Domain entities are classes. - Dependency injection everywhere: constructor injection only, no service locator, no
new-ing services. - All EF Core queries in the Data project behind repository or service interfaces defined in Core.
- Return
Results.Problem(...)/TypedResultsfrom Minimal API endpoints — correct status codes matter (201 for creation with Location header, 204 for deletes, 404 before 400 checks where relevant). - Logging via
ILogger<T>with structured message templates ("Fetched {BookId}"), never string interpolation into the log call.
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 · 63 lines · 845 tokens per session scan A b12fbf4a6778
dotnet-claude-code-kit CLAUDE.md is an instructions file published in the GitHub repository cwoodruff/dotnet-claude-code-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 845 tokens to every session, about $0.0042 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-31.
Other instructions, from other repositories
maui integration-tests.instructions.md
Guidance for GitHub Copilot when working with .NET MAUI integration tests.
maui handler-patterns.instructions.md
Instructions for dotnet/maui, covering handler mapper and property patterns, property update flow, lifecycle management, null safety in callbacks and native defaults preservation.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
cryptoexchange-net
Use CryptoExchange.Net abstractions when generating C#/.NET code that needs to work across MULTIPLE cryptocurrency exchanges (Binance + Bybit + OKX + Kraken + Coinbase + ...) — for arbitrage, best-execution routing, multi-exchange portfolio dashboards, exchange-agnostic trading bots, or comparison tools. Triggers on…
kraken-net
Use Kraken.Net when generating C#/.NET code that interacts with the Kraken cryptocurrency exchange, including Spot REST, Spot WebSocket v2, Futures REST, Futures WebSocket, account data, market data, order placement, Kraken Earn, local order books, dependency injection, or CryptoExchange.Net SharedApis. Triggers on…
Kucoin.Net copilot-instructions.md
Instructions for JKorf/Kucoin.Net, covering copilot instructions for kucoin.net, use kucoin.net, not raw http, client setup, result handling and api structure.