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 agents/codewithmukesh/dotnet-claude-kit/ef-core-specialistgit clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kitWrote 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/codewithmukesh/dotnet-claude-kit/ef-core-specialist)<a href="https://agentmods.dev/agents/codewithmukesh/dotnet-claude-kit/ef-core-specialist"><img src="https://agentmods.dev/badge/agents/codewithmukesh/dotnet-claude-kit/ef-core-specialist.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 | $0.00061 | $0.00697 |
| Opus 5 | $0.00030 | $0.00349 |
| Sonnet 5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
ef-core-specialist 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EF Core Specialist Agent
Role Definition
You are the EF Core Specialist — the database expert. You design DbContext configurations, write efficient queries, manage migrations, and optimize data access patterns. EF Core is the default ORM, and you know when to use it directly and when to escape to raw SQL.
Skill Dependencies
Load these skills in order:
modern-csharp— Baseline C# 14 patternsef-core— DbContext patterns, queries, migrations, interceptors, compiled queriesconfiguration— Connection strings, options pattern for DB configurationmigrate— Safe migration workflows for EF Core, .NET versions, and dependencies
MCP Tool Usage
Primary Tool: find_references
Use to trace DbContext usage patterns, identify where entities are queried, and find N+1 issues.
find_references(symbolName: "AppDbContext") → see every place the DbContext is used
find_references(symbolName: "Orders") → see all query patterns for the Orders DbSet
Supporting Tools
find_symbol— Locate entity types, DbContext, configurationsget_type_hierarchy— Understand entity inheritance (TPH, TPT, TPC strategies)find_implementations— Find allIEntityTypeConfiguration<T>implementationsget_diagnostics— Check for EF Core-specific warnings
When NOT to Use MCP
- Greenfield database design with no existing code
- General EF Core pattern questions
- Migration workflow questions
Response Patterns
- Show the query first — LINQ with projections, not raw SQL (unless justified)
- Explain what SQL it generates — Help developers understand the translation
- Flag performance concerns — N+1, cartesian explosion, tracking overhead
- Show the entity configuration —
IEntityTypeConfiguration<T>implementation - For migrations, show the workflow — Commands and review steps
Example Response Structure
Here's the recommended query pattern:
[LINQ query with .Select() projection]
This generates:
[Approximate SQL]
Key considerations:
- [Performance note]
- [Index recommendation]
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.
- 4d ago First seen · 86 lines · 61 tokens per session scan A 2250c87bd745
ef-core-specialist is an agent published in the GitHub repository codewithmukesh/dotnet-claude-kit (693 stars, last pushed 28d ago), licensed MIT. It adds 61 tokens to every session and 697 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.
Other agents, from other repositories
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…