dotnet-roslynator

dotnet-roslynator is a skill for Claude Code, Codex from Postpartum-genushyacinthus29/dotnet-skills. It costs 59 tokens per session (1,187 once invoked), scanned A, a copy of dotnet-roslynator, MIT.

A collection of C# analyzers and an optional command-line tool that finds code issues, unused code, and cleanup opportunities in .NET projects.

In plain words
What is it for?
Use it for build-time analysis, code fixes, formatting, unused-code searches, and cleanup workflows.
Why use it?
The standard SDK analyzers may not provide all the extra checks or automated fixes a project needs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it for build-time analysis, code fixes, formatting, unused-code searches, and cleanup workflows.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator
Install

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.

Any agent
npx skills add Postpartum-genushyacinthus29/dotnet-skills --skill dotnet-roslynator
Clone the repo
git clone --depth 1 https://github.com/Postpartum-genushyacinthus29/dotnet-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dotnet-roslynator

README.md
[![agentmods](https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator/github.svg)](https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator)
Your own site
<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator/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.

agentmods 80×15 button for dotnet-roslynator

Your own site · 80×15
<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-roslynator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 92% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01187
Opus 5 $0.00030 $0.00593
Sonnet 5 $0.00012 $0.00237
Haiku 4.5 $0.00006 $0.00119

Measured 9d ago against content hash b0c8932dafa5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

dotnet-roslynator 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 9d 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.

Origin

This is a copy

92% identical to dotnet-roslynator — 2 lines 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.

skills/dotnet-roslynator/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Roslynator

Trigger On

  • the repo uses or wants Roslynator.Analyzers
  • the team wants Roslynator CLI or extra Roslyn-based rules
  • the user asks about C# linting, static analysis, code cleanup, or unused code

Value

  • produce a concrete project delta: code, docs, config, tests, CI, or review artifact
  • reduce ambiguity through explicit planning, verification, and final validation skills
  • leave reusable project context so future tasks are faster and safer

Do Not Use For

  • repos that already have overlapping analyzer packs with no consolidation plan
  • formatting-only work when the repo already standardized on dotnet format or CSharpier

Inputs

  • the nearest AGENTS.md
  • current analyzer packages
  • .editorconfig

Quick Start

  1. Read the nearest AGENTS.md and confirm scope and constraints.
  2. Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
  3. Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

  1. Prefer the NuGet analyzer packages for build-enforced checks.
  2. Use the CLI when the repo needs one of these flows explicitly:
    • analyze
    • fix
    • find-unused
    • format
  3. Build first when Roslynator needs compiled context.
  4. Configure rule severity and Roslynator behavior in .editorconfig.
  5. Avoid duplicating the same rules across multiple analyzer packs without a severity plan.
  6. Treat CLI auto-fix as a controlled change:
    • run it on a bounded target first
    • rebuild
    • rerun tests

Bootstrap When Missing

If Roslynator is not configured yet:

  1. Detect current state:
    • rg -n "Roslynator\\.Analyzers" -g '*.csproj' .
    • rg --files -g '.config/dotnet-tools.json'
    • dotnet tool list --local
    • dotnet tool list --global
    • command -v roslynator
  2. Choose the install path deliberately:
    • analyzer package: dotnet add PROJECT.csproj package Roslynator.Analyzers
    • optional CLI: dotnet new tool-manifest (if missing) and dotnet tool install roslynator.dotnet.cli
  3. Configure ownership in root .editorconfig so Roslynator does not fight SDK analyzers, StyleCop, or Meziantou.
  4. If the CLI is adopted, add exact commands in AGENTS.md and CI, such as:
    • dotnet tool run roslynator analyze SOLUTION_OR_PROJECT
    • dotnet tool run roslynator fix SOLUTION_OR_PROJECT
  5. Run dotnet build SOLUTION_OR_PROJECT and the selected Roslynator command, then return status: configured or status: improved.
  6. If the repo wants only the current analyzer baseline and no Roslynator-specific CLI workflow, return status: not_applicable.

Read the full file on GitHub · 127 lines

Files

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.

Changes

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.

  1. 9d ago First seen · 127 lines · 59 tokens per session scan A b0c8932dafa5

Subscribe to this mod's changes

dotnet-roslynator is a skill published in the GitHub repository Postpartum-genushyacinthus29/dotnet-skills (10 stars, last pushed 2d ago), licensed MIT. It adds 59 tokens to every session and 1,187 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to dotnet-roslynator, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

dotnet-techne-cross-repo-impact

Use when reviewing a .NET pull request for breaking changes that may affect other microservice repositories. Detects cross-repo API, DTO, endpoint, EF entity, and NuGet-package breaks, and checks whether a compatible downstream PR already exists. Keywords: cross-repo impact, breaking change, microservice…

Metalnib/dotnet-episteme-skills · 95 tokens

dotnet-techne-csharp-type-design-performance

Use when designing types and collections for hot paths and low-allocation .NET code. Keywords: readonly struct, sealed class, ValueTask, Span, FrozenDictionary, FrozenSet, allocation optimisation.

Metalnib/dotnet-episteme-skills · 49 tokens

dotnet-techne-synopsis

Use when you need blast-radius analysis, dependency graphs, cross-repo impact, breaking-change diff, or architectural overview of .NET workspaces. Keywords: blast radius, dependency graph, impact analysis, cross-repo, call graph, endpoint map, EF Core lineage, breaking change, daemon, reindex.

Metalnib/dotnet-episteme-skills · 70 tokens

dotnet-techne-csharp-api-design

Use when designing or changing public C#/.NET APIs with compatibility and versioning constraints. Keywords: breaking change, API design, backward compatibility, binary compatibility, deprecation strategy, versioning.

Metalnib/dotnet-episteme-skills · 48 tokens

dotnet-techne-csharp-concurrency-patterns

Use when choosing .NET concurrency patterns for async I/O, queues, pipelines, or thread safety. Keywords: async/await, channels, dataflow, Rx, lock contention, producer consumer, parallel processing.

Metalnib/dotnet-episteme-skills · 53 tokens

dotnet-techne-inspect

Use when you need to inspect NuGet package APIs, list public types, or decompile method/property signatures. Keywords: inspect package API, list types, decompile type, method signatures, NuGet interface.

Metalnib/dotnet-episteme-skills · 49 tokens