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-featuresnpx skills add managedcode/MCPGateway --skill mcaf-dotnet-featuresgit 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.00054 | $0.01183 |
| Opus 5 | $0.00027 | $0.00592 |
| Sonnet 5 | $0.00011 | $0.00237 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
mcaf-dotnet-features 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 yesterday.
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
95% identical to dotnet-modern-csharp — 16 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: .NET Features
Trigger On
- the repo wants more modern idiomatic C# code
- a change depends on language-version compatibility
- the team is upgrading or reviewing C# feature usage across versions
- you need to know whether a C# 13 or C# 14 feature is safe to use
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
- non-C# .NET languages such as F# or VB
- analyzer-only or formatter-only setup with no language feature choice
Inputs
- target
TFMorTFMs - explicit
LangVersion, if any - current SDK version
- team style rules in
.editorconfigandAGENTS.md
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
- Detect the real language ceiling from the repo's target framework and explicit
LangVersion. - Prefer stable features that the current repo actually supports.
- Use modern syntax when it reduces ceremony, improves correctness, or makes invariants clearer.
- Do not mass-rewrite a codebase into newer syntax unless the repo wants that churn.
- Treat preview features as opt-in only. Never assume preview because the current machine has a newer SDK.
- Pay special attention to C# 13 and C# 14:
- C# 13 is the stable language for
.NET 9 - C# 14 is the stable language for
.NET 10
- C# 13 is the stable language for
- When feature selection changes architecture, style rules, or generated-code patterns, coordinate with:
mcaf-dotnetmcaf-dotnet-analyzer-configmcaf-solid-maintainability
- After feature-driven refactors, run the repo's .NET quality pass through
mcaf-dotnet.
Bootstrap When Missing
If the requested C# feature depends on SDK or language support the repo does not have yet:
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.
- yesterday First seen · 118 lines · 54 tokens per session scan A 7e8e6c71f68b
mcaf-dotnet-features is a skill published in the GitHub repository managedcode/MCPGateway (5 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,183 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to dotnet-modern-csharp, differing in 16 lines, and is treated as a copy.
Other skills, from other repositories
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).
benchmark-parity-triage
Use this when a benchmark harness exists but parity with an upstream reference implementation is unproven.
cli-wiring
Bug class: Commands implemented in packages/squad-cli/src/cli/commands/ but never routed in cli-entry.ts.
init-mode
Team initialization flow (Phase 1 proposal + Phase 2 creation).
distributed-mesh
How to coordinate with squads on different machines using git as transport.