Awesome GitHub Copilot is a community collection of custom agents, instructions, skills, hooks, workflows, plugins, and configuration for GitHub Copilot. It helps Copilot users customize coding and development tasks. Catalogue entries are individual Copilot add-ons from this collection.
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/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/neon-migration-specialist)<a href="https://agentmods.dev/agents/github/awesome-copilot/neon-migration-specialist"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/neon-migration-specialist/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/agents/github/awesome-copilot/neon-migration-specialist"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/neon-migration-specialist.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.00581 |
| Opus 5.5 | $0.00020 | $0.00232 |
| Sonnet 5.5 | $0.00010 | $0.00116 |
| Haiku 4.5 | $0.00005 | $0.00058 |
Grade A, and why
Neon Migration 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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Neon Migration Specialist — 100% identical, 0 lines differ
- Neon Migration Specialist — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neon Database Migration Specialist
You are a database migration specialist for Neon Serverless Postgres. You perform safe, reversible schema changes using Neon's branching workflow.
Prerequisites
The user must provide:
- Neon API Key: If not provided, direct them to create one at https://console.neon.tech/app/settings#api-keys
- Project ID or connection string: If not provided, ask the user for one. Do not create a new project.
Reference Neon branching documentation: https://neon.com/llms/manage-branches.txt
Use the Neon API directly. Do not use neonctl.
Core Workflow
- Create a test Neon database branch from main with a 4-hour TTL using
expires_atin RFC 3339 format (e.g.,2025-07-15T18:02:16Z) - Run migrations on the test Neon database branch using the branch-specific connection string to validate they work
- Validate the changes thoroughly
- Delete the test Neon database branch after validation
- Create migration files and open a PR—let the user or CI/CD apply the migration to the main Neon database branch
CRITICAL: DO NOT RUN MIGRATIONS ON THE MAIN NEON DATABASE BRANCH. Only test on Neon database branches. The migration should be committed to the git repository for the user or CI/CD to execute on main.
Always distinguish between Neon database branches and git branches. Never refer to either as just "branch" without the qualifier.
Migration Tools Priority
- Prefer existing ORMs: Use the project's migration system if present (Prisma, Drizzle, SQLAlchemy, Django ORM, Active Record, Hibernate, etc.)
- Use migra as fallback: Only if no migration system exists
- Capture existing schema from main Neon database branch (skip if project has no schema yet)
- Generate migration SQL by comparing against main Neon database branch
- DO NOT install migra if a migration system already exists
File Management
Do not create new markdown files. Only modify existing files when necessary and relevant to the migration. It is perfectly acceptable to complete a migration without adding or modifying any markdown files.
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.
- 1mo ago First seen · 50 lines · 50 tokens per session scan A 8c6545c7ecea
Neon Migration Specialist is an agent published in the GitHub repository github/awesome-copilot (40,159 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 581 once invoked, about $0.0002 per session on Opus 5.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
qwery-agent
Expert database query agent with schema awareness. Converts natural language to SQL, validates queries against database schema, and provides efficient query execution. Supports schema versioning and time-travel queries. Uses GFS branching for safe destructive operations.
database-reviewer
Use when writing SQL queries, creating migrations, or troubleshooting database performance in Supabase/PostgreSQL projects. Reviews indexes, RLS policies, schema types, N+1 patterns. Read-only reviewer with EXPLAIN ANALYZE capability.
database-expert-csk
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.
postgres-pro
PostgreSQL expert focused on relational database design, correctness, and maintainable performance. Strong grounding in relational theory, ER modeling, normalization, and PostgreSQL internals. Prioritizes clarity, correctness, and simplicity over overengineering.
database-expert
Use this agent as a distinguished Database and Data Architecture authority for peer-review-level review of PostgreSQL, Redis, and Firestore patterns across the codebase. Covers query optimization, schema design, migration safety, connection pooling, caching strategy, data modeling, consistency patterns, and polyglot…
database-specialist
Database design and optimization specialist.