dotnet-mcaf

A guide for adopting MCAF, a set of software-development governance practices, in a .NET repository. It organizes project instructions, documentation, installed skills, and checks for substantial work.

In plain words
What is it for?
Use it when starting or updating MCAF in a .NET solution, arranging AGENTS.md instructions, choosing governance and implementation skills, or organizing architecture, feature, testing, and operations documents.
Why use it?
Without shared project rules, developers and coding agents may follow inconsistent processes or duplicate guidance. This provides a structure for keeping development work and documentation aligned.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/managedcode/prompterone/dotnet-mcaf
Any agent
npx skills add managedcode/PrompterOne --skill dotnet-mcaf
Clone the repo
git clone --depth 1 https://github.com/managedcode/PrompterOne

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00057 $0.00980
Opus 5 $0.00028 $0.00490
Sonnet 5 $0.00011 $0.00196
Haiku 4.5 $0.00006 $0.00098

Measured 2d ago against content hash 26f34d21bdff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.codex/skills/dotnet-mcaf/SKILL.md · 88 lines

How it starts

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

MCAF Adoption

Trigger On

  • bootstrapping MCAF in a new or existing repository that also contains .NET work
  • updating root or project-local AGENTS.md files to follow a durable repo workflow
  • deciding which MCAF governance skills and dotnet-* implementation skills to install together
  • organizing repo-native docs for architecture, features, ADRs, testing, development, and operations

Workflow

  1. Start from the canonical bootstrap surface:

    • tutorial: https://mcaf.managed-code.com/tutorial
    • concepts: https://mcaf.managed-code.com/
    • public MCAF skills: https://mcaf.managed-code.com/skills
  2. Place root AGENTS.md at the repository or solution root.

  3. Add project-local AGENTS.md only when the solution has multiple projects with genuinely different local rules.

  4. Install MCAF governance skills (dotnet-mcaf-*) for process areas and dotnet-* implementation skills for framework work. Check references/skill-map.md for overlap before adding duplicate surfaces.

  5. Route to the narrowest MCAF skill once the governance concern is clear:

    Concern Skill
    Delivery workflow and feedback loops dotnet-mcaf-agile-delivery
    Developer onboarding and local inner loop dotnet-mcaf-devex
    Durable docs structure and source-of-truth placement dotnet-mcaf-documentation
    Executable feature behaviour docs dotnet-mcaf-feature-spec
    Human review for large AI-generated drops dotnet-mcaf-human-review-planning
    ML/AI product delivery process dotnet-mcaf-ml-ai-delivery
    Explicit quality attributes and trade-offs dotnet-mcaf-nfr
    Branch, merge, and release hygiene dotnet-mcaf-source-control
    Design-system, accessibility, front-end direction dotnet-mcaf-ui-ux
  6. Scaffold repo-native documentation:

    docs/
    ├── Architecture.md
    ├── Features/
    ├── ADR/
    ├── Testing/
    ├── Development/
    └── Operations/
    
  7. Encode the non-trivial task flow in AGENTS.md: <slug>.brainstorm.md then <slug>.plan.md then implementation and validation.

  8. Treat verification as part of done: tests, analyzers, formatters, coverage, and any architecture or security gates the repo configured.

Read the full file on GitHub · 88 lines

Files

What ships with it

3 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. 2d ago First seen · 88 lines · 57 tokens per session scan A 26f34d21bdff

Subscribe to this mod's changes

dotnet-mcaf is a skill published in the GitHub repository managedcode/PrompterOne (42 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 980 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

vela

Compiler-exact code search for .NET solutions - find where a symbol is defined, every reference to it, who calls it, and what a change would break. Covers C#, VB, Razor Pages, MVC views and Blazor components, which grep and every other code-intelligence tool miss. Deterministic, built on Roslyn, never modifies the…

dbhq-uk/vela-skill · 164 tokens

widget-creator

Step-by-step guide for creating new widgets in the Hex1b TUI library. Use when implementing new widgets from scratch, including widget records, nodes, extension methods, theming, reconciliation, and tests.

mitchdenny/hex1b · 46 tokens

aspire

Orchestrates Aspire distributed applications using the Aspire CLI for running, debugging, and managing distributed apps. USE FOR: aspire start, aspire stop, start aspire app, aspire describe, list aspire integrations, debug aspire issues, view aspire logs, add aspire resource, aspire dashboard, update aspire apphost.…

mitchdenny/hex1b · 150 tokens

blazorbindings-maui-third-party

Integrate third-party .NET MAUI control libraries into BlazorBindings.Maui apps by generating Razor wrappers, registering attached properties, and bridging to native elements for imperative APIs such as popups or bottom sheets. Use when adding, updating, or troubleshooting a MAUI control package in a…

Dreamescaper/BlazorBindings.Maui · 85 tokens

nina-repository

Repository-specific guidance for working in the N.I.N.A. codebase and NINA.sln. Use when Codex is asked to modify, review, test, debug, navigate, or explain code in this repository; touch NINA. projects, app startup/DI, profiles/settings, localization, database migrations, equipment, astrometry, imaging, plate…

isbeorn/nina · 106 tokens

csharp-dotnet

Use when writing, reviewing, testing, or shipping C# / .NET code — ASP.NET Core APIs (minimal APIs vs controllers), EF Core data access, async correctness, solution layout in .cs/.csproj/.sln. NOT a Java/Spring backend (that is spring-boot), NOT a Node/TypeScript backend (that is nestjs), NOT framework-neutral REST…

ericrisco/rsc-harness · 89 tokens