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 skills add AI-Unified-Process/marketplace --skill ef-migrationgit clone --depth 1 https://github.com/AI-Unified-Process/marketplaceWrote 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/skills/ai-unified-process/marketplace/ef-migration)<a href="https://agentmods.dev/skills/ai-unified-process/marketplace/ef-migration"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/ef-migration/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ai-unified-process/marketplace/ef-migration"><img src="https://agentmods.dev/badge/skills/ai-unified-process/marketplace/ef-migration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.00576 |
| Opus 5 | $0.00040 | $0.00288 |
| Sonnet 5 | $0.00016 | $0.00115 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
ef-migration 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 10d 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EF Core Database Migration
Goal
Create a native EF Core C# Migration (dotnet ef migrations add <MigrationName>) and configure entity models in DbContext based on docs/entity_model.md.
Instructions
-
Read
docs/entity_model.mdto inspect the required entities, attributes, relationships, and validation constraints. -
Inspect existing
DbContextand Entity Classes under the project solution (.csproj). -
Generate/Update Entity Classes & Configurations:
- Represent entities as C# classes with file-scoped namespaces and modern properties (
public required string Name { get; set; }). - Declare navigation properties safely for Nullable Reference Types (e.g.
public List<OrderItem> Items { get; set; } = [];orpublic Customer Customer { get; set; } = null!;). - Implement
IEntityTypeConfiguration<T>for Fluent API mappings (table names, column types,HasPrecision(18, 2)for decimal fields,HasConversion<string>()for enums, foreign keys, and unique indexes). - Register configurations in
OnModelCreating(ModelBuilder modelBuilder)(or usemodelBuilder.ApplyConfigurationsFromAssembly(...)).
- Represent entities as C# classes with file-scoped namespaces and modern properties (
-
Generate EF Core Migration:
- Run
dotnet ef migrations add UCXXX_Descriptionusing CLI. For multi-project solutions, specify project flags (e.g.dotnet ef migrations add UCXXX_Description --project src/MyApp.Data --startup-project src/MyApp.Web). - Verify the generated migration class under
Migrations/.
- Run
-
DO NOT:
- Execute destructive schema drops on production environments.
- Hardcode connection strings in source code; use
appsettings.jsonor environment variables.
-
Next Step Guidance:
- Conclude your response by summarizing the migration created and guiding the user to implementation:
"Next step: Run
/implement UC-XXX(e.g./implement UC-001) to construct your vertical slice feature."
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.
- 10d ago First seen · 42 lines · 80 tokens per session scan A 210432a07054
ef-migration is a skill published in the GitHub repository AI-Unified-Process/marketplace (123 stars, last pushed 11d ago), licensed Apache-2.0. It adds 80 tokens to every session and 576 once invoked, about $0.0004 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 skills, from other repositories
azure-resource-manager-postgresql-dotnet
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for…
optimizing-ef-core-queries
Optimize and improve the performance of slow Entity Framework Core (EF Core) queries: make them generate less SQL, make fewer database round-trips, and return results faster. Use whenever an EF Core or DbContext query or data-access path is slow or should be made faster — whether or not EF Core owns the database…
entity-framework-core
Design, tune, or review EF Core data access with proper modeling, migrations, query translation, performance, and lifetime management for modern .NET applications. USE FOR: DbContext, migrations, model configuration, EF queries, tracking, loading, performance, transactions, and EF6 migration decisions. DO NOT USE FOR…
efcore-patterns
Entity Framework Core best practices including NoTracking by default, query splitting for navigation collections, migration management, dedicated migration services, and common pitfalls to avoid.
entity-framework6
Maintain or migrate EF6-based applications with realistic guidance on what to keep, what to modernize, and when EF Core is or is not the right next step. USE FOR: EF6 codebases; runtime versus ORM migration decisions; EDMX, code-first, ObjectContext, and legacy data-access review. DO NOT USE FOR: unrelated stacks…
ef-core
Entity Framework Core patterns for .NET 10. Covers DbContext configuration, migrations workflow, interceptors, compiled queries, ExecuteUpdateAsync, ExecuteDeleteAsync, value converters, and query optimization. Load this skill when working with databases, writing queries, managing schema changes, or when the user…