What is mcaf-dotnet-analyzer-config?

A guide for configuring .NET code-analysis and style rules in .editorconfig, a repository file that controls editor and analyzer behavior. It explains how to set rule severity, formatting choices, and ownership in one main configuration.

Use it to create or review a root .editorconfig, set analyzer warnings and errors, define code-style options, and manage exceptions for tests, generated code, or legacy areas.

It helps teams avoid conflicting or hidden style settings across a .NET repository. It also clarifies when a subfolder needs stricter or different rules.

How managedcode/MCPGateway configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to managedcode/MCPGateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/managedcode/MCPGateway/main/.codex/skills/mcaf-dotnet-analyzer-config/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/managedcode/MCPGateway

Made for: 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-dotnet-analyzer-config/github.svg)](https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-dotnet-analyzer-config)

Your own site

<a href="https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-dotnet-analyzer-config"><img src="https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-dotnet-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/managedcode/mcpgateway/mcaf-dotnet-analyzer-config"><img src="https://agentmods.dev/badge/skills/managedcode/mcpgateway/mcaf-dotnet-analyzer-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,049 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 89% 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.

Model	Per session	Once invoked
Fable 5.1	$0.00066	$0.01049
Opus 5.5	$0.00026	$0.00420
Sonnet 5.5	$0.00013	$0.00210
Haiku 4.5	$0.00007	$0.00105

Measured 1mo ago against content hash 64a4f6cf76d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mcaf-dotnet-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 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.

Origin

This is a copy

89% identical to analyzer-config — 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.

.codex/skills/mcaf-dotnet-analyzer-config/SKILL.md · 111 lines

How it starts

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

MCAF: .NET Analyzer Config

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

Read the nearest AGENTS.md and confirm scope and constraints.
Run this skill's Workflow through the Ralph Loop until outcomes are acceptable.
Return the Required Result Format with concrete artifacts and verification evidence.

Workflow

Prefer one repo-root .editorconfig with root = true.
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.
Keep severity in .editorconfig, not scattered through IDE settings.
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
Keep bulk switches such as EnableNETAnalyzers in MSBuild files, not in .editorconfig.
Treat .globalconfig as an exceptional case, not the normal repo setup.

Bootstrap When Missing

If analyzer configuration is requested but not structured yet:

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

Read the full file on GitHub · 111 lines

Files

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.

references/analyzer-config.md 4.5 KB

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.

1mo ago First seen · 111 lines · 66 tokens per session scan A 64a4f6cf76d7

Subscribe to this mod's changes

mcaf-dotnet-analyzer-config is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session and 1,049 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to analyzer-config, differing in 10 lines, and is treated as a copy.

C# and .NET Languages ai-extensions dotnet embeddings mcp mcp-gateway

generate-code-cs

Generate the code from typespec for C#. Parameter: C# SDK repository root location .

Azure/azure-sdk-for-net · 26 tokens

author-test

Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.

Azure/azure-sdk-for-net · 68 tokens

opentelemetry-net-instrumentation

Provides guidance for implementing OpenTelemetry instrumentation in .NET codebases, covering tracing (Activities/Spans), metrics, logs, naming conventions, error handling, performance, SDK setup, resources, context propagation, and API design best practices.

Aaronontheweb/dotnet-skills · 56 tokens

migrate-xunit-to-mstest

Convert .NET tests from xUnit.net v2/v3 to MSTest v4 while preserving VSTest or MTP. Use for replacing xunit packages, Fact/Theory/InlineData/MemberData, assertions, IClassFixture/ICollectionFixture, ITestOutputHelper, TestContext cancellation, traits/Owner, skips, timeouts, and xUnit parallelization. Also use when a…

managedcode/dotnet-skills · 141 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

managedcode/dotnet-skills · 149 tokens

semantic-kernel

Build AI-enabled .NET applications with Semantic Kernel using services, plugins, prompts, and function-calling patterns that remain testable and maintainable. USE FOR: adding AI-driven prompts, plugins, or orchestration to a .NET app; reviewing kernel construction, service registration, or plugin usage; building…

managedcode/dotnet-skills · 116 tokens

MCPGateway: Skill for Codex