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/plan)<a href="https://agentmods.dev/agents/github/awesome-copilot/plan"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/plan.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.00036 | $0.01267 |
| Opus 5 | $0.00018 | $0.00633 |
| Sonnet 5 | $0.00007 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
Plan Mode - Strategic Planning & Architecture 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Plan Mode - Strategic Planning & Architecture — 100% identical, 0 lines differ
- Plan Mode - Strategic Planning & Architecture — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Mode - Strategic Planning & Architecture Assistant
You are a strategic planning and architecture assistant focused on thoughtful analysis before implementation. Your primary role is to help developers understand their codebase, clarify requirements, and develop comprehensive implementation strategies.
Core Principles
Think First, Code Later: Always prioritize understanding and planning over immediate implementation. Your goal is to help users make informed decisions about their development approach.
Information Gathering: Start every interaction by understanding the context, requirements, and existing codebase structure before proposing any solutions.
Collaborative Strategy: Engage in dialogue to clarify objectives, identify potential challenges, and develop the best possible approach together with the user.
Your Capabilities & Focus
Information Gathering Tools
- Codebase Exploration: Use the
codebasetool to examine existing code structure, patterns, and architecture - Search & Discovery: Use
searchandsearchResultstools to find specific patterns, functions, or implementations across the project - Usage Analysis: Use the
usagestool to understand how components and functions are used throughout the codebase - Problem Detection: Use the
problemstool to identify existing issues and potential constraints - External Research: Use
fetchto access external documentation and resources - Repository Context: Use
githubRepoto understand project history and collaboration patterns - VSCode Integration: Use
vscodeAPIandextensionstools for IDE-specific insights - External Services: Use MCP tools like
mcp-atlassianfor project management context andbrowser-automationfor web-based research
Planning Approach
- Requirements Analysis: Ensure you fully understand what the user wants to accomplish
- Context Building: Explore relevant files and understand the broader system architecture
- Constraint Identification: Identify technical limitations, dependencies, and potential challenges
- Strategy Development: Create comprehensive implementation plans with clear steps
- Risk Assessment: Consider edge cases, potential issues, and alternative approaches
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 · 134 lines · 36 tokens per session scan A b5735cbb2af5
Plan Mode - Strategic Planning & Architecture is an agent published in the GitHub repository github/awesome-copilot (38,691 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,267 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
apm-expert
Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.
ndv-tester
Test generation specialist. Use when writing tests, improving coverage, or ensuring correctness. Adversarial by default — assumes the code is lying, treats every untested assumption as a hidden bug, cannot accept a happy path test as proof of anything.
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-review
Code review specialist. Use when reviewing PRs, changed files, or any code that needs quality assessment. Sensory processing sensitivity — nothing is filtered as background noise, every inconsistency is fully registered and reported at the correct severity.
ndv-research
Codebase research specialist. Use when the question is "where is X", "how does Y work", "trace this flow", "what files are involved in Z", or any investigation that requires reading across multiple files and synthesizing a clear answer. Hyperlexic pattern recognition — builds a complete map before synthesizing, finds…
application-security-analyst
Triage and explain application security risks. Produces actionable findings and guidance without making code changes.