Borrowing it
Nothing to install: this file belongs to managedcode/Orleans.RateLimiting. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/managedcode/Orleans.RateLimiting/main/.codex/skills/roslynator/SKILL.mdgit clone --depth 1 https://github.com/managedcode/Orleans.RateLimitingWrote 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/managedcode/orleans.ratelimiting/roslynator)<a href="https://agentmods.dev/skills/managedcode/orleans.ratelimiting/roslynator"><img src="https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/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.
<a href="https://agentmods.dev/skills/managedcode/orleans.ratelimiting/roslynator"><img src="https://agentmods.dev/badge/skills/managedcode/orleans.ratelimiting/roslynator.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.01169 |
| Opus 5.5 | $0.00022 | $0.00468 |
| Sonnet 5.5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
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 19d 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.
This is a copy
97% 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.
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 formatorCSharpier
Inputs
- the nearest
AGENTS.md - current analyzer packages
.editorconfig
Quick Start
- Read the nearest
AGENTS.mdand confirm scope and constraints. - Run this skill's
Workflowthrough theRalph Loopuntil outcomes are acceptable. - Return the
Required Result Formatwith 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:
analyzefixfind-unusedformat
- 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 --localdotnet tool list --globalcommand -v roslynator
- Choose the install path deliberately:
- analyzer package:
dotnet add PROJECT.csproj package Roslynator.Analyzers - optional CLI:
dotnet new tool-manifest(if missing) anddotnet tool install roslynator.dotnet.cli
- analyzer package:
- Configure ownership in root
.editorconfigso Roslynator does not fight SDK analyzers, StyleCop, or Meziantou. - If the CLI is adopted, add exact commands in
AGENTS.mdand CI, such as:dotnet tool run roslynator analyze SOLUTION_OR_PROJECTdotnet tool run roslynator fix SOLUTION_OR_PROJECT
- Run
dotnet build SOLUTION_OR_PROJECTand the selected Roslynator command, then returnstatus: configuredorstatus: improved. - If the repo wants only the current analyzer baseline and no Roslynator-specific CLI workflow, return
status: not_applicable.
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.
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.
- 19d ago First seen · 125 lines · 56 tokens per session scan A 6dbe2bd7bc0d
roslynator is a skill published in the GitHub repository managedcode/Orleans.RateLimiting (30 stars, last pushed 11d ago), licensed MIT. It adds 56 tokens to every session and 1,169 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to dotnet-roslynator, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
profiling
Use the free official .NET diagnostics CLI tools for profiling and runtime investigation in .NET repositories. USE FOR: the repo needs performance or runtime profiling for a .NET application; the user asks about slow code, high CPU, GC pressure, allocation growth, exception storms, lock. DO NOT USE FOR: replacing…
roslyn-codelens
Use when working with any .NET / C# code (.cs/.csproj/.sln/.slnx files), finding callers/references/implementations, checking compiler errors or warnings, running dotnet build for diagnostics, searching for a type/method/interface by name, inspecting DI registrations, detecting dead code or circular dependencies…
cs0618-hunter
Detects and fixes CS0618 obsolete API warnings in .NET builds. The compiler is the authoritative source for what your project actually triggers — it catches transitive obsoletions, overload-resolution surprises, and project-local [Obsolete] attributes that static inspection cannot see. Pair with the repository-pinned…
nuget-diff-analyzer
Post-processes the repository-pinned [email protected] -- diff output into a categorised report (breaking / additive / newly-obsolete) with each finding cross-referenced to the MAF obsolete-API registry.
rider-search
Routing rules for code search in JetBrains Rider projects — use the Rider MCP symbol/reference/file tools instead of Bash grep. Use whenever searching for a symbol, definition, function, variable, type, or finding usages/references in a C#/.NET or Unreal C++ codebase open in Rider.
dotnet-performance
Evidence-first performance engineering workflow for coding agents combining portable .NET diagnostics with platform-native profiling, BenchmarkDotNet, application benchmarking, statistical validation, deployment, container, graphics, and GPU procedures.