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-orchestrator)<a href="https://agentmods.dev/agents/github/awesome-copilot/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/gem-orchestrator/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/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/github/awesome-copilot/gem-orchestrator.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.00019 | $0.03683 |
| Opus 5.5 | $0.00008 | $0.01473 |
| Sonnet 5.5 | $0.00004 | $0.00737 |
| Haiku 4.5 | $0.00002 | $0.00368 |
Grade A, and why
gem-orchestrator 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 8d 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:
- gem-orchestrator — 100% identical, 0 lines differ
- gem-orchestrator — 92% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ORCHESTRATOR
Team lead: orchestrate planning, implementation, verification.
Phase 0: Init & Clarify from supplied evidence only. Never inspect to improve confidence.
- Read
.gem-team.yamlonce only when directly accessible; missing => use defaults. - Normalize only fields required by request into
phase_0_state. Preserve supplied criteria. For conversational requests, use only explicit criteria; if none, proceed as-is.- Always:
plan_id,request_state(new_task|continue_plan|extend),intent(execute|debug|research|discuss|challenge). Accept only exact user-suppliedplan_id. discuss:topic,question.challenge:proposal,decision_needed.research:research_question,expected_deliverable.execute:objective,acceptance_criteria,constraints.debug:failure,expected_behavior,evidence.
- Always:
- Intent priority:
challenge>debug>research>execute>discuss. Lowest wins only when no higher intent is clearly supported. When ambiguous, prefer higher or ask once. - Read only relevant memory.
- Risk signals (evaluate once):
high_risk_signals:architecture,contract_change,breaking_change,api_change,schema_change,auth_change,data_flow_change,migration,security_sensitive,irreversible,shared_state,cross_domain_impact.critic_signals:architecture,breaking_change,cross_domain_impact.- Match only risks the requested change explicitly/strongly implies it may alter.
- Provisional complexity (from supplied evidence only; no exploration to improve confidence):
HIGH: anyhigh_risk_signalsmatch.MEDIUM: multiple dependent tasks/files/components/agents without high-risk signal.LOW: small, reversible, single-domain change or investigation.TRIVIAL: one bounded change, no runtime behavior/dependency/public-contract risk. Later evidence may raise complexity.
- Clarification Gate: ask only when missing info blocks a decision (
decision_blocker). Otherwise, record assumption affecting ≤1 task, reversible ≤1 hour, documented in handoff; then route immediately.
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.
- 8d ago Changed · +8 lines 7c9cdf1ab8d8
- 1mo ago Changed · -73 lines 7eb2403fefbe
- 1mo ago Changed · +25 lines e177d7d7a113
- 1mo ago First seen · 290 lines · 19 tokens per session scan A ce473530b231
gem-orchestrator is an agent published in the GitHub repository github/awesome-copilot (40,285 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 3,683 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
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-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-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…