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 agentmods add skills/nikiforovall/claude-code-rules/dotnet-analyzersnpx skills add NikiforovAll/claude-code-rules --skill dotnet-analyzersgit 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-analyzers)<a href="https://agentmods.dev/skills/nikiforovall/claude-code-rules/dotnet-analyzers"><img src="https://agentmods.dev/badge/skills/nikiforovall/claude-code-rules/dotnet-analyzers.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 | $0.00045 | $0.02016 |
| Opus 5 | $0.00023 | $0.01008 |
| Sonnet 5 | $0.00009 | $0.00403 |
| Haiku 4.5 | $0.00005 | $0.00202 |
Grade A, and why
dotnet-analyzers 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 5d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET Analyzers & Code Format
Fix code style and analyzer diagnostics using dotnet format.
Arguments: $ARGUMENTS
Key Concepts
dotnet formatdoes its own internal compilation — it does NOT depend on cached build output- CA*/SA* rules (analyzers) run during build if
EnableNETAnalyzersis true
Command Reference
| Task | Command |
|---|---|
| Fix specific style diagnostic | dotnet format style --diagnostics IDE0005 --severity warn |
| Fix specific analyzer diagnostic | dotnet format analyzers --diagnostics CA1305 --severity warn |
| Fix all style issues | dotnet format style --severity warn |
| Fix all analyzer issues | dotnet format analyzers --severity warn |
| Fix everything | dotnet format --severity warn |
| Verify only (CI) | dotnet format --verify-no-changes --severity warn |
| List violations without fixing | dotnet format style --verify-no-changes --severity warn -v diag |
| Scope to folder | dotnet format style --diagnostics IDE0005 --include src/MyProject/ |
Common Diagnostics
Style (IDE*) — use dotnet format style
| ID | Description |
|---|---|
| IDE0005 | Unnecessary using directive |
| IDE0055 | Fix formatting |
| IDE0090 | Simplify new expression |
| IDE0161 | File-scoped namespace |
| IDE0251 | Make member readonly |
Analyzers (CA*) — use dotnet format analyzers
| ID | Description |
|---|---|
| CA1305 | Specify IFormatProvider |
| CA1822 | Mark members as static |
| CA1859 | Use concrete types for performance |
| CA2000 | Dispose objects before losing scope |
Workflow
IMPORTANT: Always start in verify/list mode. NEVER auto-fix without explicit user confirmation.
Step 1: List violations (default)
Always start by showing what would change — never fix automatically.
Use --report "$TEMP/dotnet-format" to get structured JSON, then process with jq.
# List all style violations as JSON report
dotnet format style --verify-no-changes --severity warn --report "$TEMP/dotnet-format" <PROJECT_OR_SOLUTION> 2>/dev/null
# List specific diagnostic
dotnet format style --verify-no-changes --diagnostics IDE0005 --severity warn --report "$TEMP/dotnet-format" <PROJECT_OR_SOLUTION> 2>/dev/null
# List analyzer violations
dotnet format analyzers --verify-no-changes --severity warn --report "$TEMP/dotnet-format" <PROJECT_OR_SOLUTION> 2>/dev/null
What ships with it
2 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.
- 5d ago First seen · 175 lines · 45 tokens per session scan A e874f39bc12a
dotnet-analyzers is a skill published in the GitHub repository NikiforovAll/claude-code-rules (141 stars, last pushed 7d ago), licensed Apache-2.0. It adds 45 tokens to every session and 2,016 once invoked, about $0.0002 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-30.
Other skills, from other repositories
unity-coder
Use when implementing Unity C# code to follow proper coding guidelines, naming conventions, member ordering, and Unity-specific patterns.
unity-dev
Start Unity C# development workflow with architecture, implementation, review, and testing phases.
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…
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
bun-file-io
Use for Bun file I/O: Bun.file, Bun.write, streams, directories, glob patterns, metadata.