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 zdanovichnick/dotnet-pilot --skill dotnet-project-initgit clone --depth 1 https://github.com/zdanovichnick/dotnet-pilotWrote 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/zdanovichnick/dotnet-pilot/dotnet-project-init)<a href="https://agentmods.dev/skills/zdanovichnick/dotnet-pilot/dotnet-project-init"><img src="https://agentmods.dev/badge/skills/zdanovichnick/dotnet-pilot/dotnet-project-init.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.1 | $0.00029 | $0.00613 |
| Opus 5 | $0.00015 | $0.00307 |
| Sonnet 5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
dotnet-project-init 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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Project Initialization Skill
This skill discovers everything about a .NET solution needed for DotnetPilot to operate effectively.
Discovery Protocol
1. Solution File
- Search for
*.slnx(modern) or*.sln(legacy) in current directory - If multiple solutions: ask user which one to use
- Parse project references from solution file
2. Per-Project Analysis
For each project in the solution:
dotnet list <project.csproj> reference # project references
dotnet list <project.csproj> package # NuGet packages
Parse .csproj for:
<TargetFramework>→ net8.0, net9.0, net10.0, etc.<OutputType>→ Exe, Library<Sdk>→ Microsoft.NET.Sdk.Web (web), Microsoft.NET.Sdk (classlib)<IsPackable>→ library intended for NuGet distribution<RootNamespace>→ namespace convention
3. Framework Detection
| Indicator | Detection |
|---|---|
| Test runner | xunit → xunit package; NUnit → NUnit package; MSTest → MSTest.TestAdapter |
| Mocking | Moq, NSubstitute, FakeItEasy in test project packages |
| Assertions | FluentAssertions, Shouldly in test project packages |
| ORM | Microsoft.EntityFrameworkCore → EF Core; Dapper → Dapper |
| Validation | FluentValidation or DataAnnotations (check for [Required] attributes) |
| CQRS | MediatR package presence |
| Mapping | AutoMapper or Mapster package presence |
| API style | [ApiController] attribute → controllers; MapGet/MapPost → minimal API |
4. Architecture Style Detection
Analyze project reference graph:
Clean Architecture:
- Domain has 0 project references
- Application references only Domain
- Infrastructure references Domain + Application
- Api references Application + Infrastructure
Vertical Slices:
- Feature folders within a single project
- No strict layer separation
Flat:
- Single project or 2 projects (app + tests)
5. EF Core Context Discovery
Search for classes inheriting DbContext:
class *DbContext : DbContext
class *Context : DbContext
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.
- 6d ago First seen · 75 lines · 29 tokens per session scan A 339df5e3458c
dotnet-project-init is a skill published in the GitHub repository zdanovichnick/dotnet-pilot (4 stars, last pushed 10d ago), licensed MIT. It adds 29 tokens to every session and 613 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-31.
Other skills, from other repositories
language-csharp
C# and .NET idioms — .NET 8 LTS, C# NRT, records, value semantics, switch expressions, async/await, Task, ValueTask, CancellationToken, ConfigureAwait, IOptions , LINQ, Span , ArrayPool, hot path, allocation profiling, and performance. Auto-load when working with .cs files, .csproj, .sln, Directory.Build.props, or…
writing-csharp
Idiomatic C# /.NET development. Use when writing C# code, changing .csproj or .sln, or working on ASP.NET Core apps, libraries, CLIs, workers, and xUnit/NUnit/MSTest suites. Emphasizes nullable references, async/await, LINQ discipline, boundary validation, focused dotnet feedback, and minimal dependencies. NOT for Go…
dotnet-backend-expert
This skill should be used when the user is writing, reviewing, debugging, or architecting pure .NET backend code for Kestrel-hosted services. It provides expert critique for REST endpoints, SignalR hubs, TypeScript/React client integration shape, pragmatic Rust interop, application services, AppHost-aware project…
write-dotnet-code
Write and review C#/.NET code in Dynamo following Dynamo coding standards, modern C# patterns, and repo conventions. Use this skill whenever writing C# code, reviewing a PR diff, designing types, managing PublicAPI surface files, choosing patterns, making performance decisions, or refactoring in the Dynamo codebase.…
clean-dotnet-code
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.