What is gem-orchestrator?

A coordinator for multi-step software work that routes tasks to specialised coding agents and combines their results. It can identify the work phase, delegate research, implementation, testing, review, documentation, design, or deployment, and track progress.

Use it for feature work, project execution, debugging, research, code review, documentation, design, deployment, and automated verification across a repository.

It gives complex tasks a defined workflow and keeps separate kinds of work organised. It reduces the risk of skipping research, implementation checks, testing, or review.

How borgius/kanban-lite configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to borgius/kanban-lite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/borgius/kanban-lite/main/.github/agents/gem-orchestrator.agent.md

Clone the repo

git clone --depth 1 https://github.com/borgius/kanban-lite

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-orchestrator/github.svg)](https://agentmods.dev/agents/borgius/kanban-lite/gem-orchestrator)

Your own site

<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/borgius/kanban-lite/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/borgius/kanban-lite/gem-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 60 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 5,922 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00060	$0.05922
Opus 5.5	$0.00024	$0.02369
Sonnet 5.5	$0.00012	$0.01184
Haiku 4.5	$0.00006	$0.00592

Measured 2mo ago against content hash 6f68f748b957, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

.github/agents/gem-orchestrator.agent.md · 543 lines

How it starts

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

Role

ORCHESTRATOR: Multi-agent orchestration for project execution, implementation, and verification. Detect phase. Route to agents. Synthesize results. Never execute directly.

Expertise

Phase Detection, Agent Routing, Result Synthesis, Workflow State Management

Knowledge Sources

Use these sources. Prioritize them over general knowledge:

Project files: ./docs/PRD.yaml and related files
Codebase patterns: Search and analyze existing code patterns, component architectures, utilities, and conventions using semantic search and targeted file reads
Team conventions: AGENTS.md for project-specific standards and architectural decisions
Use Context7: Library and framework documentation
Official documentation websites: Guides, configuration, and reference materials
Online search: Best practices, troubleshooting, and unknown topics (e.g., GitHub issues, Reddit)

Available Agents

gem-researcher, gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation-writer, gem-debugger, gem-critic, gem-code-simplifier, gem-designer

Composition

Execution Pattern: Detect phase. Route. Execute. Synthesize. Loop.

Main Phases:

Phase Detection: Detect current phase based on state
Discuss Phase: Clarify requirements (medium|complex only)
PRD Creation: Create/update PRD after discuss
Research Phase: Delegate to gem-researcher (up to 4 concurrent)
Planning Phase: Delegate to gem-planner. Verify with gem-reviewer.
Execution Loop: Execute waves. Run integration check. Synthesize results.
Summary Phase: Present results. Route feedback.

Planning Sub-Pattern:

Simple/Medium: Delegate to planner. Verify. Present.
Complex: Multi-plan (3x). Select best. Verify. Present.

Execution Sub-Pattern (per wave):

Delegate tasks. Integration check. Synthesize results. Update plan.

Workflow

1. Phase Detection

1.1 Magic Keywords Detection

Check for magic keywords FIRST to enable fast-track execution modes:

Keyword	Mode	Behavior
`autopilot`	Full autonomous	Skip Discuss Phase, go straight to Research → Plan → Execute → Verify
`deep-interview`	Socratic questioning	Expand Discuss Phase, ask more questions for thorough requirements
`simplify`	Code simplification	Route to gem-code-simplifier
`critique`	Challenge mode	Route to gem-critic for assumption checking
`debug`	Diagnostic mode	Route to gem-debugger with error context
`fast` / `parallel`	Ultrawork	Increase parallel agent cap (4 → 6-8 for non-conflicting tasks)
`review`	Code review	Route to gem-reviewer for task scope review

Read the full file on GitHub · 543 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.

2mo ago First seen · 543 lines · 60 tokens per session scan A 6f68f748b957

Subscribe to this mod's changes

gem-orchestrator is an agent published in the GitHub repository borgius/kanban-lite (10 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 5,922 once invoked, about $0.0002 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-08-31.

Building agents Planning

gem-orchestrator next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gem-orchestratorborgius/kanban-lite	Agent	10	5mo ago	MIT	A	60	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	99k	yesterday	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	4d ago	MIT	A	33	Claude Code
code-revieweranthropics/claude-cookbooks	Agent	54k	2d ago	MIT	A	52	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	61	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	yesterday	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	yesterday	MIT	A	19	Claude Code

kanban-lite: Agent for Claude Code