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/github/awesome-copilot/oracle-to-postgres-migration-expertgit clone --depth 1 https://github.com/github/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/github/awesome-copilot/oracle-to-postgres-migration-expert)<a href="https://agentmods.dev/agents/github/awesome-copilot/oracle-to-postgres-migration-expert"><img src="https://agentmods.dev/badge/agents/github/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 | $0.00041 | $0.03067 |
| Opus 5 | $0.00020 | $0.01533 |
| Sonnet 5 | $0.00008 | $0.00613 |
| Haiku 4.5 | $0.00004 | $0.00307 |
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 today.
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 — 140 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.
- 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 during Phases 5 and 6 (code and test migration) — do not alter tables, views, indexes, constraints, sequences, or other schema objects (except stored procedures, which may be corrected in Phase 6 per the fix loop instructions) while the application code is being migrated. DDL creation is only permitted in Phase 4, and even then only generate scripts for the user to apply — never apply DDL directly.
- Never apply database changes directly on behalf of the user. Generate scripts and explicit run instructions so the user applies DB changes themselves.
- 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.
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.
- today First seen · 140 lines · 41 tokens per session scan A 61490baefcb0
Oracle-to-PostgreSQL Migration Expert is an agent published in the GitHub repository github/awesome-copilot (38,592 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 3,067 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
database-architect
Expert database architect for schema design, query optimization, migrations, and modern serverless databases. Use for database operations, schema changes, indexing, and data modeling. Triggers on database, sql, schema, migration, query, postgres, index, table.
dnp-ef-migration-planner
🗄️ EF Core migration safety — validates migration chain, detects data loss risks, ensures correct DbContext targeting.
ndv-refactor
Code transformation specialist. Use when renaming, extracting, restructuring, or modernizing syntax. OCD form — incorrect structure is not a style preference, it is an intolerable state that must be corrected incrementally and completely.
ndv-diagnose
Debugging specialist. Use when you have a bug, failing test, stack trace, unexpected behavior, or anything broken that needs a root cause — not a guess. Locks onto the problem and will not stop until the cause is confirmed, not just located.
ndv-explain
Technical documentation writer. Use when creating or updating docs, API references, session notes, or any written material explaining code to humans. Never assumes shared context — models the reader's knowledge gap and bridges it deliberately.
data-modeling-architect
Dimensional modeling architect for dbt projects. Designs fact and dimension tables following Kimball methodology, plans model DAG structure, defines grain and measures, and architects the layer strategy for new analytics features. Use PROACTIVELY when designing new data models or planning model dependencies.