What is dotnet-roslynator?

A set of free tools for checking C# code, finding unused code, cleaning up projects, and applying some automatic fixes. It uses Roslyn, the code-analysis system built into the .NET ecosystem, and can also provide a command-line tool.

Use it for build-enforced code checks, C# cleanup, dead-code detection, automatic fixes, formatting, and optional command-line analysis in projects or continuous-integration checks.

It adds extra C# checks beyond the analyzers included with the .NET software development kit and helps catch issues before they reach review or production.

dotnet-roslynator — Skill by managedcode

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.

agentmods

npx agentmods add skills/managedcode/prompterone/dotnet-roslynator

Any agent

npx skills add managedcode/PrompterOne --skill dotnet-roslynator

Clone the repo

git clone --depth 1 https://github.com/managedcode/PrompterOne

Made for: Claude Code, Codex.

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,172 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found 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.

Model	Per session	Once invoked
Fable 5	$0.00059	$0.01172
Opus 5	$0.00030	$0.00586
Sonnet 5	$0.00012	$0.00234
Haiku 4.5	$0.00006	$0.00117

Measured 2d ago against content hash 4e536623a0b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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

Copies of this mod

2 near-identical copies found in the catalogue:

mcaf-dotnet-roslynator — 91% identical, 8 lines differ
mcaf-dotnet-roslynator — 91% identical, 8 lines differ

.codex/skills/dotnet-roslynator/SKILL.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 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

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

Workflow

Prefer the NuGet analyzer packages for build-enforced checks.
Use the CLI when the repo needs one of these flows explicitly:
- analyze
- fix
- find-unused
- format
Build first when Roslynator needs compiled context.
Configure rule severity and Roslynator behavior in .editorconfig.
Avoid duplicating the same rules across multiple analyzer packs without a severity plan.
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:

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
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
Configure ownership in root .editorconfig so Roslynator does not fight SDK analyzers, StyleCop, or Meziantou.
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
Run dotnet build SOLUTION_OR_PROJECT and the selected Roslynator command, then return status: configured or status: improved.
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 · 125 lines

Files

What ships with it

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

2d ago First seen · 125 lines · 59 tokens per session scan A 4e536623a0b3

Subscribe to this mod's changes

dotnet-roslynator is a skill published in the GitHub repository managedcode/PrompterOne (42 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 1,172 once invoked, about $0.0003 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.

blazor blazor-webassembly csharp dotnet livestreaming presentation

vela

Compiler-exact code search for .NET solutions - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Covers C#, VB, Razor Pages, MVC views and Blazor components, which grep and every other code-intelligence tool miss. Deterministic, built on Roslyn, never modifies the…

dbhq-uk/vela-skill · 164 tokens

widget-creator

Step-by-step guide for creating new widgets in the Hex1b TUI library. Use when implementing new widgets from scratch, including widget records, nodes, extension methods, theming, reconciliation, and tests.

mitchdenny/hex1b · 46 tokens

aspire

Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost.…

mitchdenny/hex1b · 150 tokens

dotnet-roslynator