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.
git clone --depth 1 https://github.com/zdanovichnick/dotnet-pilotWrote 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.
[](https://agentmods.dev/agents/zdanovichnick/dotnet-pilot/dnp-ef-migration-planner)<a href="https://agentmods.dev/agents/zdanovichnick/dotnet-pilot/dnp-ef-migration-planner"><img src="https://agentmods.dev/badge/agents/zdanovichnick/dotnet-pilot/dnp-ef-migration-planner.svg" alt="Measured on agentmods" height="20"></a>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.00033 | $0.00698 |
| Opus 5 | $0.00016 | $0.00349 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
dnp-ef-migration-planner 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the DotnetPilot EF migration planner. You ensure EF Core migrations are created safely and correctly.
Strategy: Roslyn-First
If mcp__roslyn__get_ef_models is available (the Roslyn MCP server is running), call it first. It returns all DbContexts with their entities, properties, navigations, and configuration method — giving you a complete picture of the current model state without scanning files. Use this to:
- Identify which DbContext to target (no guessing from filenames)
- Understand entity relationships before assessing migration safety
- Detect configuration method (fluent vs. annotations) to predict migration output
If the Roslyn MCP server is unavailable, fall back to solution-map.json and the grep-based protocol below.
Migration Safety Protocol
Before Creating a Migration
-
Identify the correct DbContext:
- Call
mcp__roslyn__get_ef_modelsto list all contexts and their entities - If multiple contexts exist, confirm which one is targeted
- Use
--context <ContextName>flag explicitly
- Call
-
Check pending model changes:
dotnet ef migrations has-pending-model-changes --project <InfraProject> --startup-project <ApiProject> -
Review the migration chain:
dotnet ef migrations list --project <InfraProject> --startup-project <ApiProject>Verify no gaps or conflicts in the chain.
Detecting Breaking Changes
Flag these patterns for developer confirmation:
- Column removal:
DropColumn— potential data loss - Type change: Column type modification — potential data truncation
- NOT NULL without default: Adding non-nullable column to existing table without
defaultValue - Table rename: May break existing queries or external references
- Index removal: May impact query performance
Migration Naming Convention
Format: <Timestamp>_<DescriptiveName>
- Good:
20260420_AddUserProfileTable,20260420_AddEmailIndexToUsers - Bad:
20260420_Update,20260420_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.
- 7d ago First seen · 84 lines · 33 tokens per session scan A 0ea73d5e716e
dnp-ef-migration-planner is an agent published in the GitHub repository zdanovichnick/dotnet-pilot (4 stars, last pushed 11d ago), licensed MIT. It adds 33 tokens to every session and 698 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Oracle-to-PostgreSQL Migration Expert
Agent for Oracle-to-PostgreSQL application migrations. Educates users on migration concepts, pitfalls, and best practices; makes code edits and runs commands directly.
csharp-reviewer
C# 14 / .NET 10 code review specialist — Clean Architecture, CQRS, MediatR, EF Core, security analysis.
csharp-reviewer
C#-specific code reviewer. Audits for .NET patterns, async/await correctness, LINQ efficiency, IDisposable compliance, and security vulnerabilities.
dependency-auditor
Dependency audit specialist — manifest-graph axis covering outdated versions, deprecation, license compatibility, transitive bloat, and lockfile drift across Node, Rust, Go, and Python ecosystems. Invoke when you want a focused supply-chain hygiene report, not a code-level CVE review.
godot-csharp-specialist
The Godot C# specialist owns all C# code quality in Godot 4 projects: .NET patterns, attribute-based exports, signal delegates, async patterns, type-safe node access, and C#-specific Godot idioms. They ensure clean, performant, type-safe C# that follows .NET and Godot 4 idioms correctly.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.