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/cwoodruff/dotnet-claude-code-kit/add-endpointnpx skills add cwoodruff/dotnet-claude-code-kit --skill add-endpointgit clone --depth 1 https://github.com/cwoodruff/dotnet-claude-code-kitWrote 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/cwoodruff/dotnet-claude-code-kit/add-endpoint)<a href="https://agentmods.dev/skills/cwoodruff/dotnet-claude-code-kit/add-endpoint"><img src="https://agentmods.dev/badge/skills/cwoodruff/dotnet-claude-code-kit/add-endpoint.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.00041 | $0.00391 |
| Opus 5 | $0.00020 | $0.00196 |
| Sonnet 5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
add-endpoint 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 4d 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.
This is a copy
100% identical to add-endpoint — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Add a Minimal API Endpoint
Task: implement $ARGUMENTS end to end.
- Read the neighborhood first. Open the existing endpoint group for this resource (or the closest one) and mirror its structure exactly: MapGroup usage, TypedResults unions, DTO records, DI parameters.
- Define contracts. Request/response DTOs as
recordtypes. Never expose EF entities. - Wire the data path. If a needed repository/service method doesn't exist, add the interface method in Core, implement it in Data with async EF Core +
CancellationToken, and register it if new. - Implement the endpoint with:
TypedResultsunion return type- Input validation before any database call, returning
ValidationProblemon failure - Correct status codes (201 + Location on create via
CreatedAtRoute/Created, 204 on delete, 404 on missing) CancellationTokenthreaded through- Structured logging for failures only (don't log every request)
- Write tests in the Tests project: at least one happy path and one failure path per endpoint, named
MethodName_Scenario_ExpectedResult. UseWebApplicationFactory<Program>for integration coverage. - Verify.
dotnet build --nologothendotnet test --nologo --filterscoped to the new tests. Report results. - Summarize the new route, its status codes, and any follow-ups (auth, pagination, caching) you deliberately left out.
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.
- 4d ago First seen · 23 lines · 41 tokens per session scan A c1ee239bfccd
add-endpoint is a skill published in the GitHub repository cwoodruff/dotnet-claude-code-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 391 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to add-endpoint, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
agents-sdk-dotnet
Use when any code imports Microsoft.Agents.Hosting.AspNetCore, Microsoft.Agents.Builder, or related Agents SDK packages, or when the user is building, configuring, or asking questions about a Microsoft 365 Agents SDK agent in C# / .NET. Trigger on questions about appsettings.json, connection configuration…
agents-sdk-dotnet-otel
Use when adding, configuring, validating, or troubleshooting OpenTelemetry observability for a Microsoft 365 Agents SDK application in C# / .NET. Trigger when the user mentions OpenTelemetry, OTel, telemetry, traces, metrics, logs, OTLP, Aspire Dashboard, Application Insights, Azure Monitor, distributed tracing…
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
agents-sdk-dotnet-debugging
Use when troubleshooting an agent built with the Microsoft Agents SDK (Microsoft.Agents.Hosting.AspNetCore and related packages) in C# / .NET. Trigger on any of these symptoms: build or C# compile errors, crashes on startup, 401 or auth errors on incoming requests, the bot not responding to messages, appsettings.json…
nunit-api-design
Use when adding or modifying public API surface in NUnit — new or changed constraints, attributes, assertions, helpers, or any type/member visibility change. Covers the conventions NUnit maintainers enforce for types that ship to consumers of the framework.