dotnet-resharper-clt

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

A set of JetBrains command-line tools for inspecting and cleaning up C# and .NET code using shared project settings.

In plain words
What is it for?
Use it to run solution-level inspections, apply cleanup profiles, and enforce ReSharper settings from the command line.
Why use it?
The default .NET analyzers may not cover all of a team's inspection and cleanup rules. These tools can apply consistent checks and cleanup in local or CI workflows.

Skill for Claude CodeCodex

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

Good fit Use it to run solution-level inspections, apply cleanup profiles, and enforce ReSharper settings from the command line.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-resharper-clt
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-resharper-clt
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-resharper-clt

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-resharper-clt"><img src="https://agentmods.dev/badge/skills/postpartum-genushyacinthus29/dotnet-skills/dotnet-resharper-clt.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,360 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 94% 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.00071 $0.01360
Opus 5 $0.00036 $0.00680
Sonnet 5 $0.00014 $0.00272
Haiku 4.5 $0.00007 $0.00136

Measured 8d ago against content hash 485ec0257b1e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dotnet-resharper-clt 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 8d 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

94% identical to resharper-clt — 12 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-resharper-clt/SKILL.md · 134 lines

How it starts

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

ReSharper Command Line Tools

Trigger On

  • the repo uses or wants ReSharper Command Line Tools
  • the team wants jb inspectcode or jb cleanupcode
  • the user asks for stronger C# inspections, cleanup profiles, or ReSharper-based CI gates

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

  • replacing tests with inspection output
  • ad-hoc formatting-only work when the repo intentionally standardizes on another formatter
  • repos that do not want JetBrains settings or CLT-based gates in their workflow

Inputs

  • the nearest AGENTS.md
  • the target .sln, .csproj, or bounded file set
  • repo-root .editorconfig
  • solution shared settings such as YourSolution.sln.DotSettings

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 solution-level runs when possible so ReSharper can resolve references and apply full inspections.
  2. Build the solution before jb cleanupcode when working at solution scope.
  3. Use jb inspectcode first to surface issues before editing anything broad.
  4. Treat surfaced issues as mandatory fixes when this gate is enabled for the repo; do not just dump a report and stop.
  5. Use jb cleanupcode with an explicit cleanup profile:
    • Built-in: Full Cleanup
    • Built-in: Reformat Code
    • Built-in: Reformat & Apply Syntax Style
    • or a checked-in custom profile
  6. Keep durable ReSharper settings in the team-shared solution layer and commit the solution .DotSettings file when policy changes.
  7. Re-run jb inspectcode after cleanup or fixes, then run the repo's normal quality pass and tests.

Read the full file on GitHub · 134 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. 8d ago First seen · 134 lines · 71 tokens per session scan A 485ec0257b1e

Subscribe to this mod's changes

dotnet-resharper-clt is a skill published in the GitHub repository Postpartum-genushyacinthus29/dotnet-skills (10 stars, last pushed 2d ago), licensed MIT. It adds 71 tokens to every session and 1,360 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to resharper-clt, differing in 12 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-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-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-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