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.
npx agentmods add agents/borgius/kanban-lite/gem-orchestratorgit clone --depth 1 https://github.com/borgius/kanban-liteWrote 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/borgius/kanban-lite/gem-orchestrator)<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="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 | $0.00060 | $0.05922 |
| Opus 5 | $0.00030 | $0.02961 |
| Sonnet 5 | $0.00012 | $0.01184 |
| Haiku 4.5 | $0.00006 | $0.00592 |
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 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.
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.yamland 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.mdfor 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 |
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 · 543 lines · 60 tokens per session scan A 6f68f748b957
gem-orchestrator is an agent published in the GitHub repository borgius/kanban-lite (7 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 5,922 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.