AI-powered toolkit for Microsoft Agent Framework (MAF) migrations — agents, skills, MCP server, and self-updating guide
Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
Agent
Use when you need a best-practice / drift audit of a clean MAF 1.3.0 codebase. Distinct from @maf-auditor (which generates a migration plan). This reviewer assumes you are ALREADY on 1.3.0 and asks 'is this code idiomatic, secure, observable, and identity-safe?' Output: audit-report.md, NOT migration-plan.md.
Agent
Use when migrating an app FROM Semantic Kernel (C#) TO Microsoft Agent Framework (MAF) — a cross-framework port, NOT a MAF version upgrade. Inventories SK usage, classifies every construct (🌉 bridge / 🔁 rewrite / 🏗 re-architect), writes a plan, scaffolds a NEW MAF project beside the original (non-destructive), and…
Agent
Use when a deployed MAF 1.3.0 app has hit a runtime failure (exception trace, hung workflow, silent workflow exit, agent loop, cost spike, prompt-injection symptom). Walks back from the symptom to the MAF pattern responsible, cross-references the obsolete-API registry + constraints, and proposes the deterministic fix.…
Agent
Use when migrating a .NET codebase to Microsoft Agent Framework (MAF) 1.3.0. Orchestrates the full migration using specialized skills for API lookup, plan generation, CS0618 detection, and fan-out validation. Handles NuGet package updates, namespaces, executors, sessions, workflows, streaming, events, and DevUI guards.
Agent
Use when a developer is joining a MAF 1.3.0 codebase for the first time and needs a guided tour: the agent topology, the workflow graph, the top-touched files, and the canonical patterns this team uses. Output: a personalised onboarding brief, not a generic README.
Agent
Use when a MAF 1.3.0 migration has regressed in production and the team needs to roll back to a known-good MAF 1.2.0 baseline surgically (not via blanket git revert). Inverse of @maf-migration. Plans the rollback as a tracked rollback-plan.md with build-verified per-task reverts.
Agent
The primary entry point for the maf-autopilot toolkit. Use this when you're not sure which specialist to invoke. @maf triages your request, calls the right MCP tool directly when one suffices, or recommends a specialist agent (@maf-migration, @maf-cross-migration, @maf-auditor, @maf-best-practice-reviewer…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: