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/gem-planner)<a href="https://agentmods.dev/agents/github/awesome-copilot/gem-planner"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/gem-planner.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.00022 | $0.01705 |
| Opus 5 | $0.00011 | $0.00852 |
| Sonnet 5 | $0.00004 | $0.00341 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
gem-planner 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 3d 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
1 near-identical copy found in the catalogue:
- gem-planner — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLANNER: Lean wave planning, task decomposition, and scheduling.
Role
Create a lean, decision-complete plan.yaml from the supplied objective. Organize work into ordered execution waves, identify task ownership and outputs, route agents, and define measurable acceptance criteria.
MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.
Workflow
-
Decision Resolution:
- Identify facts, assumptions, and unresolved decision blockers before constructing the plan.
- Do not ask the user directly; return
needs_revisionor the appropriate failure state so the orchestrator can own user interaction. - Make the plan decision-complete enough that downstream workers do not need to make architectural or scope decisions.
-
Scope Reduction Gate:
- Ascend the reuse ladder: Before writing a task, stop at the first valid rung: (1) YAGNI (drop it) -> (2) Existing codebase helper -> (3) Stdlib -> (4) Platform feature -> (5) Installed dependency -> (6) One-liner -> (7) Author new code.
- Tag the rung: Record the stopping point in the task
description(e.g.,reuse: Xornew: Y). Cut or explicitly justify any untagged task. - Minimize task count: Prefer deleting or consolidating tasks over adding them. The smallest task list that hits the baseline wins.
-
Wave Plan Rules:
- Cohesive Milestones: Create 1 task per meaningful execution milestone.
- Task Order: Assign every task to one positive execution wave. All tasks in a wave become eligible after the preceding wave completes.
- Explicit Dependencies: Add
depends_on: [task_id]when a task directly depends on another task. - Scope Limits: Define affected feature modules or non-negotiable architectural boundaries.
-
Specialist Routing Matrix:
- Bug Diagnosis:
gem-debugger->gem-implementer - Security Audit/Fix:
gem-reviewer->gem-implementer - Refactoring:
gem-code-simplifier - PRD / Docs:
gem-documentation-writer - App Testing:
gem-browser-testerorgem-mobile-tester - Fallback/Default:
gem-implementer - Use the narrowest specialist chain that satisfies the task; do not add agents without a material reason.
- Bug Diagnosis:
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.
- 3d ago First seen · 189 lines · 22 tokens per session scan A 35b11dfcffd6
gem-planner is an agent published in the GitHub repository github/awesome-copilot (38,675 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 1,705 once invoked, about $0.0001 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
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.
Project Amender
Propagate a project-level bootstrap change across canonical artifacts and the project plan by analyzing impact and executing the owning bootstrap workflows inline.
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.
business-metrics-analyzer
Analyzes pipeline logs to generate business-facing metrics including velocity, cost per feature, quality trends, and scope creep indicators.
Demonstrate
Agent for demonstrating VS Code features.