analyzer-config

analyzer-config is a skill for Claude Code, Codex from managedcode/dotnet-skills. It costs 128 tokens per session (1,132 once invoked), scanned A, original, MIT.

A repository configuration tool for .NET analyzer and style rules using a root .editorconfig file, which records code-quality settings in the project.

In plain words
What is it for?
It is for setting analyzer ownership, code-style options, section layout, and exceptions for areas such as tests or generated code.
Why use it?
It gives the team one clear place to define rule severity, formatting choices, and which settings apply to different parts of the codebase.

Skill for Claude CodeCodex

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

Good fit It is for setting analyzer ownership, code-style options, section layout, and exceptions for areas such as tests or generated code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/managedcode/dotnet-skills/analyzer-config
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 managedcode/dotnet-skills --skill analyzer-config
Clone the repo
git clone --depth 1 https://github.com/managedcode/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 analyzer-config

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/managedcode/dotnet-skills/analyzer-config"><img src="https://agentmods.dev/badge/skills/managedcode/dotnet-skills/analyzer-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 128 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,132 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00128 $0.01132
Opus 5 $0.00064 $0.00566
Sonnet 5 $0.00026 $0.00226
Haiku 4.5 $0.00013 $0.00113

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

Security

Grade A, and why

analyzer-config 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

Copies of this mod

4 near-identical copies found in the catalogue:

catalog/Tools/Analyzer-Config/skills/analyzer-config/SKILL.md · 113 lines

How it starts

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

.NET Analyzer Configuration

Trigger On

  • the repo needs a root .editorconfig
  • analyzer severity and style ownership are unclear
  • the team wants one source of truth for rule configuration

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

  • choosing analyzers with no config change
  • formatting-only execution with no config ownership question

Inputs

  • the nearest AGENTS.md
  • current .editorconfig
  • any Directory.Build.props overrides

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 one repo-root .editorconfig with root = true.
  2. Add nested .editorconfig files when a subtree has a clear scoped purpose, such as stricter rules, different generated-code handling, or a different policy for tests or legacy code.
  3. Keep severity in .editorconfig, not scattered through IDE settings.
  4. Write the file as real EditorConfig, not as a made-up .NET variant:
    • lowercase filename .editorconfig
    • root = true in the preamble
    • no inline comments
    • forward slashes in globs
  5. Keep bulk switches such as EnableNETAnalyzers in MSBuild files, not in .editorconfig.
  6. Treat .globalconfig as an exceptional case, not the normal repo setup.

Bootstrap When Missing

If analyzer configuration is requested but not structured yet:

  1. Detect current state:
    • rg --files -g '.editorconfig' -g '.globalconfig'
    • rg -n "EnableNETAnalyzers|AnalysisLevel|AnalysisMode" -g '*.csproj' -g 'Directory.Build.*' .
  2. Create or normalize one repo-root .editorconfig with root = true.
  3. Move rule severity into .editorconfig and keep bulk analyzer switches in project or MSBuild config.
  4. Add nested .editorconfig files only when a subtree really needs different scoped policy.
  5. Run dotnet build SOLUTION_OR_PROJECT and return status: configured or status: improved.
  6. If the repo intentionally uses another documented analyzer-config ownership model, return status: not_applicable.

Read the full file on GitHub · 113 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.

  1. 8d ago First seen · 113 lines · 128 tokens per session scan A 7fd74b30db8d

Subscribe to this mod's changes

analyzer-config is a skill published in the GitHub repository managedcode/dotnet-skills (478 stars, last pushed 6d ago), licensed MIT. It adds 128 tokens to every session and 1,132 once invoked, about $0.0006 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-09-03.

Related

Other skills, from other repositories

winui-setup

Install and verify the prerequisites the win-dev-skills WinUI 3 toolchain depends on — .NET SDK 8.0.100+, WinApp CLI 0.6+, and Developer Mode. Use only when the user explicitly asks to set up or repair the toolchain. Do not invoke automatically when another skill reports a missing prerequisite; tell the user what is…

microsoft/win-dev-skills · 88 tokens

winui-wpf-migration

Migrate WPF applications to WinUI 3 — namespace replacement (System.Windows → Microsoft.UI.Xaml), control mapping (DataGrid→ListView, WrapPanel→ItemsRepeater, TabControl→TabView), threading (Dispatcher→DispatcherQueue), imaging (System.Drawing→BitmapImage), MVVM conversion to CommunityToolkit.Mvvm, and…

microsoft/win-dev-skills · 100 tokens

opengis-skills

Use when AI coding assistant needs GIS/CAD/C#/AI/IoT/3D domain expertise for 75 open-source projects. One-stop skill index with tag-based search and on-demand loading for GDAL, GeoServer, QGIS, PostGIS, JTS, CesiumJS, FreeCAD, OpenSCAD, OCCT, NPOI, SqlSugar, Furion, Dify, SuperSplat, Go and more.

znlgis/opengis-skills · 96 tokens

jackson-3-migration

Migrer Jackson 2.x til Jackson 3.x (tools.jackson) i Kotlin/Java-prosjekter — automatisert OpenRewrite-pass pluss manuell Kotlin-spesifikk opprydding og verifisering.

navikt/copilot · 53 tokens

java-to-kotlin

Trinnvis Java-til-Kotlin-migrering med rammeverk-bevisste transformasjoner for Spring, Ktor og Nav-mønstre.

navikt/copilot · 35 tokens

rust-development

Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.

navikt/copilot · 27 tokens