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/claude-code-rules --skill dotnet-verifygit clone --depth 1 https://github.com/NikiforovAll/claude-code-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/claude-code-rules/dotnet-verify)<a href="https://agentmods.dev/skills/nikiforovall/claude-code-rules/dotnet-verify"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/dotnet-verify/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/claude-code-rules/dotnet-verify"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/dotnet-verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00519 |
| Opus 5.5 | $0.00027 | $0.00208 |
| Sonnet 5.5 | $0.00014 | $0.00104 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
dotnet-verify 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.
What it actually says
.NET Verify Snapshot Testing
Manage Verify snapshot tests using the verify.tool dotnet local tool.
Discovery
To list all test files using Verify snapshots:
rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs
To scope to a specific directory:
rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs <path/to/test/directory>
Update Snapshots
To update snapshots after intentional code changes:
-
Build the solution:
dotnet build -p:WarningLevel=0 /clp:ErrorsOnly --verbosity minimal -
Run affected verify tests (they fail, generating
.received.files):dotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m -
Accept all new snapshots:
dotnet verify accept -yTo scope to a specific directory:
dotnet verify accept -y -w <path/to/test/directory> -
Re-run tests to confirm they pass:
dotnet test <test-project> --no-build --filter "FullyQualifiedName~<TestClass>" -v m
File Conventions
ClassName.MethodName.verified.txt— accepted snapshot (committed to git)ClassName.MethodName.received.txt— latest test output (not committed, gitignored)- Parameterized tests:
ClassName.MethodName_param=value.verified.txt
Quick Reference
| Command | Purpose |
|---|---|
dotnet verify accept -y |
Accept all pending snapshots |
dotnet verify accept -y -w <dir> |
Accept snapshots in specific directory |
rg -l "Verifier\.Verify|UsesVerify|\.verified\." --type cs |
List all test files using Verify |
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 · 65 lines · 68 tokens per session scan A 8f18ce8cb2b9
dotnet-verify is a skill published in the GitHub repository NikiforovAll/claude-code-rules (142 stars, last pushed 23d ago), licensed Apache-2.0. It adds 68 tokens to every session and 519 once invoked, about $0.0003 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
go-tdd
Implement a Go feature using TDD methodology with up-to-date library documentation from Context7.
go-blackbox
Detect white box Go tests and propose conversion to black box tests (package footest), creating exporttest.go bridges when tests need access to internals.
rust-formal-verification
Use when Rust code, especially unsafe or panic-critical paths, needs a Kani, Verus, or Creusot harness written, run, and its failure read. Not for choosing the proof policy: use proof-driven.
unity-coder
Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns.
run-tests
Auto-detect the project's test runner (Taskfile, Makefile, go test, npm, pytest, cargo) and run it, reporting pass or fail.
typescript-testing
TypeScript testing patterns with Jest/Vitest including unit tests, integration tests, mocking strategies, and coverage. Use when writing TypeScript tests.