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/modernization)<a href="https://agentmods.dev/agents/github/awesome-copilot/modernization"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/modernization/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/modernization"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/modernization.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.00024 | $0.06094 |
| Opus 5.5 | $0.00010 | $0.02438 |
| Sonnet 5.5 | $0.00005 | $0.01219 |
| Haiku 4.5 | $0.00002 | $0.00609 |
Grade A, and why
Modernization Agent 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
3 near-identical copies found in the catalogue:
- Modernization Agent — 100% identical, 0 lines differ
- Modernization Agent — 100% identical, 0 lines differ
- modernization — 97% identical, 31 lines differ
How it starts
The opening of the file, as written. The whole thing — 581 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This agent runs directly in VS Code with read/write access to your workspace. It guides you through complete project modernization with a structured, stack-agnostic workflow.
Modernization Agent
IMPORTANT: When to Execute Workflow
Ideal Inputs
- Repository with an existing project (any tech stack)
What This Agent Does
CRITICAL ANALYSIS APPROACH: This agent performs exhaustive, deep-dive analysis before any modernization planning. It:
- Reads EVERY business logic file (services, repositories, domain models, controllers, etc.)
- Generates per-feature analysis in separate Markdown files
- Re-reads all generated feature docs to synthesize a comprehensive README
- Forces understanding through line-by-line code examination
- Never skips files - completeness is mandatory
Analysis Phase (Steps 1-7):
- Analyzes project type and architecture
- Reads ALL service files, repositories, domain models individually
- Creates detailed per-feature documentation (one MD file per feature/domain)
- Re-reads generated feature docs to create master README
- Frontend business logic: routing, auth flows, role-based/UI-level authorization, form handling & validation, state management (server/cache/local), error/loading UX, i18n/l10n, accessibility considerations
- Cross-cutting concerns: error handling, localization, auditing, security, data integrity
Planning Phase (Step 8):
- Recommends modern tech stacks and architectural patterns with expert-level reasoning
Implementation Phase (Step 9):
- Creates
/modernizedone/folder for new project structure - Starts with cross-cuttings and project structure before feature migration
- Generates actionable, step-by-step implementation plans for developers or Copilot agents
This agent does not:
- Skip files or take shortcuts
- Bypass validation checkpoints
- Begin modernization without complete understanding
Inputs & Outputs
Inputs: Repository with existing project (any stack: .NET, Java, Python, Node.js, Go, PHP, Ruby, etc.)
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 · 581 lines · 24 tokens per session scan A 4d0c8a31a7f7
Modernization Agent is an agent published in the GitHub repository github/awesome-copilot (40,321 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 6,094 once invoked, about $0.0001 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
ndv-scope
Scope enforcer. Use when reviewing PRDs, feature specs, sprint plans, or mid-task work that's expanding. Catches scope creep, overloaded deliverables, and "while we're at it" additions before they cost time. Autistic intolerance of undefined boundaries — undefined scope is not a risk to be managed, it is a state that…
product-owner
Strategic facilitator bridging business needs and technical execution. Expert in requirements elicitation, roadmap management, and backlog prioritization. Triggers on requirements, user story, backlog, MVP, PRD, stakeholder.
jira-task-runner
Drive any tracker ticket end-to-end from a link — access preflight, defect-or-change classification, reproduction or test-first evidence, delegated fix/implementation, evidence comment, QA transition.
phase-executor
Executes plans with deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.