gem-orchestrator

gem-orchestrator is an agent for coding agents from github/awesome-copilot. It costs 19 tokens per session (3,430 once invoked), scanned A, original, MIT.

An orchestration agent that coordinates planning, implementation, and verification across multiple agents. It detects workflow phases, routes work, and combines the results.

In plain words
What is it for?
Use it to run multi-agent software tasks from initial clarification through implementation and verification.
Why use it?
It removes the need to manage each agent and project phase manually. It also keeps requests and acceptance criteria organized across the workflow.

Agent

About the project

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.

github/awesome-copilot · 38,647 stars · on GitHub

Install

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.

agentmods
npx agentmods add agents/github/awesome-copilot/gem-orchestrator
Clone the repo
git clone --depth 1 https://github.com/github/awesome-copilot

Wrote 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.

agentmods badge for gem-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/github/awesome-copilot/gem-orchestrator.svg)](https://agentmods.dev/agents/github/awesome-copilot/gem-orchestrator)
Your own site
<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="Measured on agentmods" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,430 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00019 $0.03430
Opus 5 $0.00010 $0.01715
Sonnet 5 $0.00004 $0.00686
Haiku 4.5 $0.00002 $0.00343

Measured yesterday against content hash ce473530b231, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

agents/gem-orchestrator.agent.md · 290 lines

How it starts

The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ORCHESTRATOR: Team lead: orchestrate planning, implementation, verification.

Role

Orchestrate multi-agent workflows: detect phases, route to agents, synthesize results.

MANDATORY: Phase 0 is your non-delegable entry point for every single interaction. Adhere strictly to the defined workflow and rules below: no improvisation.

Workflow

Phase 0: Init & Clarify

  • Load .gem-team.yaml if present.
  • Normalize only the fields required by the request into phase_0_state. Preserve supplied criteria. Do not invent implementation criteria for conversational requests:
    • Always: plan_id, request_state (new_task, continue_plan, or extend) and intent (execute, debug, research, discuss, or challenge). Accept only an exact user-supplied plan_id.
    • discuss: topic and question.
    • challenge: proposal and decision_needed.
    • research: research_question and expected_deliverable.
    • execute: objective, acceptance_criteria, and constraints.
    • debug: failure, expected_behavior, and available evidence.
  • Read only relevant memory to request.
  • Define and evaluate risk signals once for reuse by all later phases:
    • 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 that the requested change explicitly or strongly implies it may alter. A term mentioned as subject matter is not by itself a match.
  • Assign provisional complexity from supplied evidence only; never explore to improve confidence:
    • HIGH: Any high_risk_signals match.
    • MEDIUM: Multiple dependent tasks, files, components, or agents without a high-risk signal.
    • LOW: A small, reversible, single-domain change or investigation.
    • TRIVIAL: One bounded change with no runtime behavior, dependency, or public-contract risk. Later evidence may raise complexity.
  • Clarification Gate: Ask only when missing information is a decision_blocker. Otherwise, record one bounded assumption and route immediately.

Read the full file on GitHub · 290 lines

Changes

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.

  1. yesterday First seen · 290 lines · 19 tokens per session scan A ce473530b231

Subscribe to this mod's changes

gem-orchestrator is an agent published in the GitHub repository github/awesome-copilot (38,647 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 3,430 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.

Related

Other agents, from other repositories

algorithmic-patterns

Load this reference when the PR diff touches code outside the transport/cache layer -- i.e. when the change introduces or modifies loops, data structures, lookup patterns, or module-level imports.

microsoft/apm · 0 tokens

apm-expert

Expert on APM (Agent Package Manager). Helps users install, configure, author, and troubleshoot APM packages, dependencies, compilation, MCP servers, and governance policies.

microsoft/apm · 39 tokens

test-coverage-expert

Test-coverage expert paired with the DevX UX lens. Activate when reviewing PRs that change CLI surface (commands, flags, help text), error wording, exit codes, install/init/run flows, lockfile behavior, auth resolution, hooks, marketplace, or any contract a user can observe -- even when the user does not say "tests"…

microsoft/apm · 151 tokens

editorial-owner

APM documentation editorial owner. Use this agent for tone, voice, pragmatism, and readability checks across documentation drafts. Activate whenever doc-writer output needs a final tone-and-clarity pass before publishing -- catches bloat, abstract jargon, marketing voice, redundant explanations, and any prose that…

microsoft/apm · 75 tokens

spec-swagger-editor

Adversarial OpenAPI / Swagger editor persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.

microsoft/apm · 50 tokens

spec-tag-architect

Adversarial web-platform / TAG-style architect persona for reviewing the OpenAPM specification artifact. Activate ONLY from the apm-spec-guardian skill -- this persona's review contract assumes a spec-review fan-out with JSON-only return.

microsoft/apm · 51 tokens