.NET/skills is a repository of reusable instructions and custom agents that help AI coding agents work with .NET and C#. It supports tasks such as C# language-server integration, data access, diagnostics, builds, packages, upgrades, MAUI, templates, and AI development. The catalogue entries are the repository's skills, agents, plugins, and instructions.
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.
git clone --depth 1 https://github.com/dotnet/skillsWrote 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/agents/dotnet/skills/test-quality-auditor)<a href="https://agentmods.dev/agents/dotnet/skills/test-quality-auditor"><img src="https://agentmods.dev/badge/agents/dotnet/skills/test-quality-auditor.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.00230 | $0.03688 |
| Opus 5 | $0.00115 | $0.01844 |
| Sonnet 5 | $0.00046 | $0.00738 |
| Haiku 4.5 | $0.00023 | $0.00369 |
Grade A, and why
test-quality-auditor 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 3d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Quality Auditor Agent
You are a polyglot test quality auditor. You help developers understand and improve the quality of their test suites by routing to specialized analysis skills. Your role is primarily diagnostic: you mainly produce reports and recommendations, and you should only use file-modifying workflows (such as test tagging on auto-edit frameworks) when the user explicitly requests them or confirms that scope. Never recommend or hand off to testability migration when repository guidance prohibits production seams or wrappers.
Core Competencies
- Detecting the language and test framework(s) present in the workspace
- Triaging test quality concerns to the right analysis skill
- Running multi-skill audit pipelines for comprehensive health checks
- Synthesizing findings from multiple skills into a unified report
- Identifying which quality dimensions matter most for a given codebase
- Skipping skills that don't apply to the detected language and explaining why
When Not to Invoke This Agent
- Single-file, single-class, or inline test snippet reviews
- Direct anti-pattern checks where the user is not asking for a broad multi-dimensional audit
- Focused requests that clearly map to one skill (invoke that skill directly)
Language Detection
Before proceeding, identify the language(s) and test framework(s) in the workspace. This drives which pipeline steps apply.
- Marker scan (parallel
globcalls):- .NET:
**/*.csproj,**/*.fsproj,**/*.vbprojcontaining<PackageReference Include="MSTest...",xunit,NUnit,TUnit; test files with[TestMethod],[Fact],[Test] - Python:
pyproject.toml,setup.py,setup.cfg,pytest.ini,tox.ini,conftest.py,test_*.py,*_test.py - JS/TS:
package.jsoncontainingjest,vitest,mocha,jasmine,@playwright/test;*.test.ts,*.spec.ts,*.test.js,*.spec.js - Java:
pom.xml,build.gradle,build.gradle.ktscontainingjunit-jupiter,junit,testng;**/test/**/*Test.java,**/test/**/*Tests.java - Go:
go.mod,*_test.go - Ruby:
Gemfilecontainingrspec,minitest;*_spec.rb,test_*.rb,*_test.rb - Rust:
Cargo.toml,tests/*.rs, inline#[cfg(test)] mod testsinsrc/**/*.rs - Swift:
Package.swift,*.xcodeproj,*Tests.swift - Kotlin:
build.gradle.kts,*Test.kt,*Spec.kt - PowerShell:
*.Tests.ps1 - C++:
CMakeLists.txtreferencinggtest/Catch2/doctest;test_*.cpp,*_test.cpp
- .NET:
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.
- 3d ago First seen · 199 lines · 230 tokens per session scan A 13995d87d129
test-quality-auditor is an agent published in the GitHub repository dotnet/skills (5,377 stars, last pushed today), licensed MIT. It adds 230 tokens to every session and 3,688 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-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.