Borrowing it
Nothing to install: this file belongs to managedcode/PrompterOne. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/PrompterOne/main/.codex/skills/dotnet-project-setup/SKILL.mdgit clone --depth 1 https://github.com/managedcode/PrompterOneWrote 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/managedcode/prompterone/dotnet-project-setup)<a href="https://agentmods.dev/skills/managedcode/prompterone/dotnet-project-setup"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/dotnet-project-setup/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/managedcode/prompterone/dotnet-project-setup"><img src="https://agentmods.dev/badge/skills/managedcode/prompterone/dotnet-project-setup.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.00417 |
| Opus 5.5 | $0.00016 | $0.00167 |
| Sonnet 5.5 | $0.00008 | $0.00083 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
dotnet-project-setup 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- project-setup — 100% identical, 2 lines differ
- dotnet-project-setup — 94% identical, 2 lines differ
What it actually says
.NET Project Setup
Trigger On
- creating a new .NET solution or restructuring an existing one
- setting up
Directory.Build.props, shared package management, or repo-wide defaults - defining project layout for apps, libraries, and test projects
Workflow
- Start from the app model and deployment target, then choose the smallest correct SDK and target framework set.
- Use solution folders and project names that reflect bounded contexts or product areas, not temporary implementation details.
- Centralize shared build settings, analyzer rules, nullable context, and package versions where it reduces duplication without hiding important differences.
- Create test projects and CI hooks early so new projects do not drift into unverified templates.
- Prefer project references and composition over circular dependencies or utility dumping grounds.
- Document the local build, test, and run path in repo docs or
AGENTS.mdwhen the workflow is not obvious.
Deliver
- a coherent solution structure
- shared build defaults that are easy to reason about
- starter quality and testing hooks for future work
Validate
- projects have explicit responsibility boundaries
- shared MSBuild settings do not accidentally override platform-specific needs
- a new contributor can build and test the repo without guessing
References
- patterns.md: solution layout conventions,
Directory.Build.props,Directory.Build.targets, Central Package Management,global.json,nuget.config, analyzers, multi-targeting, and source link - templates.md:
dotnet newtemplates for console apps, class libraries, ASP.NET Core APIs, worker services, Blazor, test projects, .NET Aspire, and gRPC services
What ships with it
3 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.
- 1mo ago First seen · 40 lines · 41 tokens per session scan A b9e54899ecdf
dotnet-project-setup is a skill published in the GitHub repository managedcode/PrompterOne (45 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 417 once invoked, about $0.0002 per session on Opus 5.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
qa-tester
Verifies programmer deliveries when a ticket reaches Review. Actually runs the application/tests/endpoints to confirm the change works, sets up missing test tooling when needed, and blocks the ticket if execution is impossible. Posts a PASS/FAIL/BLOCKED report; on FAIL, returns the ticket to Todo.
author-test
Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.
migrate-xunit-to-mstest
Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…
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…
crap-score
Calculates CRAP (Change Risk Anti-Patterns) for a named .NET method, class, or file. USE FOR: explicit CRAP calculation or coverage-and-complexity risk within that named target, including which tests to prioritize. DO NOT USE FOR: project-wide coverage/CRAP, plateaus, or project-wide blockers/priorities…
nunit
Write, run, or repair .NET tests that use NUnit. Use when a repo uses NUnit, [Test], [TestCase], [TestFixture], or NUnit3TestAdapter for VSTest or Microsoft.Testing.Platform execution. USE FOR: writing or reviewing NUnit tests; using [Test], [TestCase], [TestFixture], [SetUp], [TearDown] attributes; configuring…