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 AratKruglik/claude-sdlc --skill dotnet-toolinggit clone --depth 1 https://github.com/AratKruglik/claude-sdlcWrote 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/aratkruglik/claude-sdlc/dotnet-tooling)<a href="https://agentmods.dev/skills/aratkruglik/claude-sdlc/dotnet-tooling"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/dotnet-tooling/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/skills/aratkruglik/claude-sdlc/dotnet-tooling"><img src="https://agentmods.dev/badge/skills/aratkruglik/claude-sdlc/dotnet-tooling.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 88 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 163 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00217 | $0.01932 |
| Opus 5 | $0.00109 | $0.00966 |
| Sonnet 5 | $0.00043 | $0.00386 |
| Haiku 4.5 | $0.00022 | $0.00193 |
Grade A, and why
dotnet-tooling 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 11d 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 — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Tooling (stack-agnostic)
Project detection
Determine the project structure at the start of every task:
| Signal | Meaning |
|---|---|
*.sln exists |
Solution file — multiple projects; use dotnet build <solution>.sln |
Single *.csproj in root |
Single-project layout |
global.json exists |
SDK version is pinned — read it first |
Directory.Build.props exists |
Solution-wide MSBuild properties apply |
Directory.Packages.props exists |
Central Package Management is active — do not specify versions in individual .csproj files |
dotnet CLI — core commands
Always run dotnet commands from the directory containing the .sln or .csproj (or pass the path explicitly).
# Restore NuGet packages
dotnet restore
# Build (all projects in the solution, or a single project)
dotnet build
dotnet build MyApp.sln
dotnet build src/MyApp/MyApp.csproj
# Run (application project)
dotnet run --project src/MyApp/MyApp.csproj
# Run tests
dotnet test
dotnet test --filter "Category=Unit"
dotnet test --logger "trx;LogFileName=results.trx"
# Publish (Release, self-contained optional)
dotnet publish -c Release -o ./publish
dotnet publish -c Release --runtime linux-x64 --self-contained
# Check outdated packages
dotnet list package --outdated
# Format code (respects .editorconfig)
dotnet format
# Verify formatting without writing changes (useful in CI)
dotnet format --verify-no-changes
global.json — pin the SDK version
{
"sdk": {
"version": "8.0.404",
"rollForward": "latestPatch"
}
}
Always read global.json first to learn which SDK version is in use. Do not recommend commands or features that require a higher SDK version than what is pinned.
rollForward: "latestPatch" allows minor patch upgrades automatically — safe for CI. Use "disable" for strict reproducibility.
.csproj — project file conventions
<Project Sdk="Microsoft.NET.Sdk">
<PropertyGroup>
<TargetFramework>net8.0</TargetFramework> <!-- or net9.0, net10.0 -->
<Nullable>enable</Nullable> <!-- always enable -->
<ImplicitUsings>enable</ImplicitUsings> <!-- reduces boilerplate using directives -->
<TreatWarningsAsErrors>true</TreatWarningsAsErrors> <!-- recommended for new projects -->
<AnalysisLevel>latest</AnalysisLevel> <!-- Roslyn analyzers at latest rules set -->
</PropertyGroup>
<ItemGroup>
<!-- With Central Package Management: version goes in Directory.Packages.props -->
<PackageReference Include="Microsoft.Extensions.Logging.Abstractions" />
<PackageReference Include="Newtonsoft.Json" />
<!-- Without CPM: pin versions explicitly — no floating ranges -->
<!-- <PackageReference Include="Serilog" Version="4.1.0" /> -->
</ItemGroup>
</Project>
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.
- 11d ago First seen · 247 lines · 217 tokens per session scan A 576da242125a
dotnet-tooling is a skill published in the GitHub repository AratKruglik/claude-sdlc (33 stars, last pushed 6d ago), licensed MIT. It adds 217 tokens to every session and 1,932 once invoked, about $0.0011 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
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
dotnet-reverse
A guide for analyzing compiled .NET and C# programs, including managed Windows executables and libraries. Reverse engineering means studying compiled software to understand how it works, and decompiling turns it back into readable approximate source code.
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-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…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
migrate-dotnet8-to-dotnet9
Migrate a .NET 8 project to .NET 9 and resolve all breaking changes. USE FOR: upgrading TargetFramework from net8.0 to net9.0, fixing build errors after updating the .NET 9 SDK, resolving behavioral changes in .NET 9 / C# 13 / ASP.NET Core 9 / EF Core 9, replacing BinaryFormatter (now always throws), resolving…