Borrowing it
Nothing to install: this file belongs to managedcode/dotPilot. 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/dotPilot/main/.codex/skills/mcaf-dotnet-resharper-clt/SKILL.mdgit clone --depth 1 https://github.com/managedcode/dotPilotWrote 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/dotpilot/mcaf-dotnet-resharper-clt)<a href="https://agentmods.dev/skills/managedcode/dotpilot/mcaf-dotnet-resharper-clt"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-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.
<a href="https://agentmods.dev/skills/managedcode/dotpilot/mcaf-dotnet-resharper-clt"><img src="https://agentmods.dev/badge/skills/managedcode/dotpilot/mcaf-dotnet-resharper-clt.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.00073 | $0.01341 |
| Opus 5.5 | $0.00029 | $0.00536 |
| Sonnet 5.5 | $0.00015 | $0.00268 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
mcaf-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 1mo 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
92% identical to resharper-clt — 10 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: .NET ReSharper CLT
Trigger On
- the repo uses or wants ReSharper Command Line Tools
- the team wants
jb inspectcodeorjb 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
- 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 solution-level runs when possible so ReSharper can resolve references and apply full inspections.
- Build the solution before
jb cleanupcodewhen working at solution scope. - Use
jb inspectcodefirst to surface issues before editing anything broad. - Treat surfaced issues as mandatory fixes when this gate is enabled for the repo; do not just dump a report and stop.
- Use
jb cleanupcodewith an explicit cleanup profile:Built-in: Full CleanupBuilt-in: Reformat CodeBuilt-in: Reformat & Apply Syntax Style- or a checked-in custom profile
- Keep durable ReSharper settings in the team-shared solution layer and commit the solution
.DotSettingsfile when policy changes. - Re-run
jb inspectcodeafter cleanup or fixes, then run the repo's normal quality pass and tests.
What ships with it
1 file 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.
- 1mo ago First seen · 130 lines · 73 tokens per session scan A 1c0f59999be3
mcaf-dotnet-resharper-clt is a skill published in the GitHub repository managedcode/dotPilot (25 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 1,341 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to resharper-clt, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
resharper-clt
Use the free official JetBrains ReSharper Command Line Tools for .NET repositories. USE FOR: jb inspectcode; jb cleanupcode; stronger C# inspections, cleanup profiles, and CI-friendly JetBrains analysis. DO NOT USE FOR: replacing tests with inspection output; ad-hoc formatting-only work when the repo intentionally…
roslynator
Use the open-source free Roslynator analyzer packages and optional CLI for .NET. USE FOR: Roslynator.Analyzers setup; Roslynator CLI checks or cleanup; C# linting, static analysis, and code-fix automation. DO NOT USE FOR: overlapping analyzer packs with no consolidation plan; formatting-only work owned by another…
stylecop-analyzers
Use the open-source free StyleCop.Analyzers package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide. USE FOR: the repo wants StyleCop.Analyzers; naming, layout, or documentation style needs stronger enforcement…
dotnet-best-practices
Ensure .NET/C# code follows maintainable, modern best practices. Use when reviewing or improving C# code, solution structure, async patterns, dependency injection, or testability.
cratis-engineering-csharp-conventions
Apply the Cratis C# house conventions when writing or reviewing C# in a Cratis repository - formatting, naming, records and primary constructors, nullable handling, XML documentation, custom exceptions, structured logging, dependency injection, and service lifetimes. Use for any "how should this be written" C# style…
quickdup
Use the open-source free QuickDup clone detector for .NET repositories. Use when a repo needs duplicate C# code discovery, structural clone detection, DRY refactoring candidates, or repeatable duplication. USE FOR: the repo wants QuickDup; the team needs repeatable duplicate-code scans for C#; the user asks about DRY…