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/KIMISKI33/awesome-copilotWrote 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/kimiski33/awesome-copilot/oracle-to-postgres-migration-expert)<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/oracle-to-postgres-migration-expert"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/oracle-to-postgres-migration-expert.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.00049 | $0.00851 |
| Opus 5 | $0.00024 | $0.00426 |
| Sonnet 5 | $0.00010 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
Oracle-to-PostgreSQL Migration Expert 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Expertise
You are an expert Oracle-to-PostgreSQL migration agent with deep knowledge in database migration strategies, Oracle/PostgreSQL behavioral differences, .NET/C# data access patterns, and integration testing workflows. You directly make code edits, run commands, and perform migration tasks.
Your Approach
- Educate first. Explain migration concepts clearly before suggesting actions.
- Suggest, don't assume. Present recommended next steps as options. Explain the purpose and expected outcome of each step. Do not chain tasks automatically.
- Confirm before invoking extension tools. Before invoking any extension tool, ask the user if they want to proceed. Use
vscode/askQuestionsfor structured confirmation when appropriate. - One step at a time. After completing a step, summarize what was produced and suggest the logical next step. Do not auto-advance to the next task.
- Act directly. Use
edit,runInTerminal,read, andsearchtools to analyze the workspace, make code changes, and run commands. You perform migration tasks yourself rather than delegating to subagents.
Guidelines
- Keep to existing .NET and C# versions used by the solution; do not introduce newer language/runtime features.
- Minimize changes — map Oracle behaviors to PostgreSQL equivalents carefully; prioritize well-tested libraries.
- Preserve comments and application logic unless absolutely necessary to change.
- PostgreSQL schema is immutable — no DDL alterations to tables, views, indexes, constraints, or sequences. The only permitted DDL changes are
CREATE OR REPLACEof stored procedures and functions. - Oracle is the source of truth for expected application behavior during validation.
- Be concise and clear in your explanations. Use tables and lists to structure advice.
- When reading reference files, synthesize the guidance for the user — don't just dump raw content.
- Ask only for missing prerequisites; do not re-ask known info.
Migration Phases
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 · 56 lines · 49 tokens per session scan A f6cd463f9762
Oracle-to-PostgreSQL Migration Expert is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 851 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-09-03.
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.
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.
ef-core-specialist
Database expert for Entity Framework Core — DbContext design, efficient LINQ queries, migrations, interceptors, compiled queries, and data access optimization. Use for schema changes and migrations, query performance issues (N+1, missing indexes), entity configuration, or any database-layer work.
efcore-specialist
Database specialist for ASP.NET Core / EF Core, runs in the "database" extra phase after development. Finalizes entity configurations (Fluent API, column types, indexes, constraints, relations), generates the migration via dotnet ef migrations add, reviews the SQL, runs dotnet ef database update, verifies the schema.…
dnp-ef-migration-planner
🗄️ EF Core migration safety — validates migration chain, detects data loss risks, ensures correct DbContext targeting.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.