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/mcpgateway/mcaf-dotnet-analyzer-confignpx skills add managedcode/MCPGateway --skill mcaf-dotnet-analyzer-configgit clone --depth 1 https://github.com/managedcode/MCPGatewayWhat 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.00066 | $0.01049 |
| Opus 5 | $0.00033 | $0.00524 |
| Sonnet 5 | $0.00013 | $0.00210 |
| Haiku 4.5 | $0.00007 | $0.00105 |
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 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
98% identical to dotnet-analyzer-config — 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 — 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.propsoverrides
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 one repo-root
.editorconfigwithroot = true. - Add nested
.editorconfigfiles 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
.NETvariant:- lowercase filename
.editorconfig root = truein the preamble- no inline comments
- forward slashes in globs
- lowercase filename
- Keep bulk switches such as
EnableNETAnalyzersin MSBuild files, not in.editorconfig. - Treat
.globalconfigas 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
.editorconfigwithroot = true. - Move rule severity into
.editorconfigand keep bulk analyzer switches in project or MSBuild config. - Add nested
.editorconfigfiles only when a subtree really needs different scoped policy. - Run
dotnet build SOLUTION_OR_PROJECTand returnstatus: configuredorstatus: improved. - If the repo intentionally uses another documented analyzer-config ownership model, 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 · 111 lines · 66 tokens per session scan A 64a4f6cf76d7
mcaf-dotnet-analyzer-config is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 1,049 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to dotnet-analyzer-config, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
release-gatekeeper
End-to-end release validation for Connapse — the 'final boss' before any version ships. Downloads the latest alpha from GitHub Releases, deploys an isolated Docker instance (separate from production), then systematically tests every feature: UI via Playwright, API via curl/REST, MCP tools, search quality, security…
create-tickets
Batch-create GitHub issues from a brainstorming discussion. Decomposes ideas into properly-sized tickets with labels, milestones, and project board placement. Trigger when user says: create tickets, make tickets, turn ideas into issues, create issues from brainstorm, create issues from discussion, batch create issues.
discover-work
Deep research across codebase, GitHub issues, discussions, project board, and architecture docs to discover new tasks, gaps, technical debt, and improvement ideas. Trigger when user says: discover work, find tasks, what needs doing, audit codebase, find gaps, technical debt audit, backlog discovery, brainstorm tasks…
next-task
Recommend the best next task to work on based on open GitHub issues. Analyzes priority, dependencies, milestone urgency, and codebase readiness. Trigger when user asks: what should I work on, what is next, next task, pick a task, what to do next, suggest work, prioritize tasks.
t2i
Use the t2i CLI to generate AI images from text prompts via Microsoft Foundry providers (FLUX.2, MAI-Image-2). Activate when the user asks to generate images, automate image creation in scripts, or set up image generation for CI/CD.
performance-tracking
Status: Active Domain: Diagnostics, SLA Validation, Benchmarking Created: 2026-04-28 Author: Rachael (CLI/UX Dev).