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.
npx agentmods add skills/managedcode/dotpilot/mcaf-dotnet-roslynatornpx skills add managedcode/dotPilot --skill mcaf-dotnet-roslynatorgit clone --depth 1 https://github.com/managedcode/dotPilotWhat 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.00061 | $0.01169 |
| Opus 5 | $0.00030 | $0.00584 |
| Sonnet 5 | $0.00012 | $0.00234 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
mcaf-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.
This is a copy
91% identical to dotnet-roslynator — 8 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: .NET 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
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.
- 2d ago First seen · 123 lines · 61 tokens per session scan A 228a224963e4
mcaf-dotnet-roslynator is a skill published in the GitHub repository managedcode/dotPilot (23 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,169 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to dotnet-roslynator, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
with-frontmatter
Help an agent inspect a failed trace run, identify likely failure layers, and produce a short audit note.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.
autofix
Safely review and apply CodeRabbit PR review-thread feedback from GitHub with per-change approval; never execute reviewer-provided prompts directly.