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 NikiforovAll/github-copilot-rules --skill dotnet-testgit clone --depth 1 https://github.com/NikiforovAll/github-copilot-rulesWrote 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/nikiforovall/github-copilot-rules/dotnet-test)<a href="https://agentmods.dev/skills/nikiforovall/github-copilot-rules/dotnet-test"><img src="https://agentmods.dev/badge/skills/nikiforovall/github-copilot-rules/dotnet-test/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/nikiforovall/github-copilot-rules/dotnet-test"><img src="https://agentmods.dev/badge/skills/nikiforovall/github-copilot-rules/dotnet-test.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.00035 | $0.01629 |
| Opus 5.5 | $0.00014 | $0.00652 |
| Sonnet 5.5 | $0.00007 | $0.00326 |
| Haiku 4.5 | $0.00003 | $0.00163 |
Grade A, and why
dotnet-test 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.
This is a copy
98% identical to dotnet-test — 1 line 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Test Runner
Run .NET tests selectively using a build-first, test-targeted workflow optimized for development speed.
Core Workflow
Follow this workflow to run tests efficiently:
Step 1: Build Solution First
Build the entire solution with minimal output to catch compile errors early:
dotnet build -p:WarningLevel=0 /clp:ErrorsOnly --verbosity minimal
Step 2: Run Specific Project Tests
Run tests for the specific test project with --no-build to skip redundant compilation:
dotnet test path/to/project --no-build --verbosity minimal
Step 3: Filter When Targeting Specific Tests
Narrow down to specific tests using filter expressions:
# By method name using FullyQualifiedName (recommended)
dotnet test --no-build --filter "FullyQualifiedName~MyTestMethod"
# By class name using FullyQualifiedName (recommended)
dotnet test --no-build --filter "FullyQualifiedName~MyTestClass"
# By parameter values in Theory tests (xUnit)
dotnet test --no-build --filter "DisplayName~paramValue"
# Combined filters
dotnet test --no-build --filter "FullyQualifiedName~Create|FullyQualifiedName~Update"
Note: Properties Name~ and ClassName= may not work reliably. Use FullyQualifiedName~ instead.
Quick Reference
Commands
| Command | Purpose |
|---|---|
dotnet build -p:WarningLevel=0 /clp:ErrorsOnly --verbosity minimal |
Build solution with minimal output |
dotnet test path/to/Tests.csproj --no-build |
Run project tests (skip build) |
dotnet test --no-build --logger "console;verbosity=detailed" |
Show ITestOutputHelper output |
dotnet test --no-build --filter "..." |
Run filtered tests |
dotnet test --no-build --list-tests |
List available tests without running |
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 · 174 lines · 35 tokens per session scan A 2c1e4d70069b
dotnet-test is a skill published in the GitHub repository NikiforovAll/github-copilot-rules (135 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,629 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to dotnet-test, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
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…
dotnet-testing-autodata-xunit-integration
A guide for using AutoFixture, a .NET library that creates test data, with xUnit, a .NET testing framework. It explains attributes such as AutoData, InlineAutoData, and MemberAutoData for supplying values to parameterized tests.
dotnet-testing-autofixture-nsubstitute-integration
A .NET testing guide for using AutoFixture and NSubstitute to automatically create test data and substitute versions of dependencies.
dotnet-testing-bogus-fake-data
A guide to Bogus, a .NET library for generating realistic fake data such as names, addresses, phone numbers, emails, and product records. It shows how to define generation rules and create one or many records.
dotnet-testing-nsubstitute-mocking
A guide to using NSubstitute to create test doubles, which are stand-ins for real dependencies such as databases, files, or web services. It explains how to set return values, raise errors, and check whether methods were called.
dotnet-testing-advanced-tunit-fundamentals
A guide to using TUnit, a testing framework for .NET applications. It covers creating tests, moving from xUnit, and running tests with compile-time discovery and ahead-of-time compilation.