agentmods.dev

gem-team: Agent for Claude Code

.apm/agents/gem-orchestrator.agent.md

gem-orchestrator is an agent for Claude Code from mubaidr/gem-team. It costs 19 tokens per session (3,683 once invoked), scanned A, a copy of gem-orchestrator, Apache-2.0.

A team-lead workflow for coordinating planning, implementation, and verification across multiple agents. It organizes requests into phases such as clarification, research, execution, debugging, or discussion.

In plain words
What is it for?
Use it to coordinate multi-agent projects, initialize or continue plans, handle implementation and debugging work, and combine results from planning and verification.
Why use it?
It provides a consistent way to understand the request, preserve its acceptance criteria and constraints, assess risks, and route work to the appropriate agents.

Agent for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions subagents.

This is mubaidr/gem-team's own configuration. It tells Claude Code how to work on gem-team itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gem-team configures →

not rated 227repo +1 changed 8d ago A scan 19 tokens copy · 92% Apache-2.0
View source ↗ mubaidr/gem-team mubaidr.github.io
Reuse

Borrowing it

Nothing to install: this file belongs to mubaidr/gem-team. 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/mubaidr/gem-team/main/.apm/agents/gem-orchestrator.agent.md
Clone the repo
git clone --depth 1 https://github.com/mubaidr/gem-team

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.

agentmods badge for gem-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/mubaidr/gem-team/gem-orchestrator/github.svg)](https://agentmods.dev/agents/mubaidr/gem-team/gem-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/mubaidr/gem-team/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/mubaidr/gem-team/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.

agentmods 80×15 button for gem-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/mubaidr/gem-team/gem-orchestrator"><img src="https://agentmods.dev/badge/agents/mubaidr/gem-team/gem-orchestrator.svg" alt="Reviewed on agentmods" width="80" 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,683 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 92% copy Near-identical to another mod 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.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

Measured 8d ago against content hash 7c9cdf1ab8d8, 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 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.

Origin

This is a copy

92% identical to gem-orchestrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.apm/agents/gem-orchestrator.agent.md · 250 lines

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.yaml once 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-supplied plan_id.
    • discuss: topic, question.
    • challenge: proposal, decision_needed.
    • research: research_question, expected_deliverable.
    • execute: objective, acceptance_criteria, constraints.
    • debug: failure, expected_behavior, evidence.
  • 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: any high_risk_signals match.
    • 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.

Read the full file on GitHub · 250 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. 8d ago Changed · -1 lines 7c9cdf1ab8d8
  2. 19d ago Changed · +1 lines bf7fdf4a41e7
  3. 23d ago Changed 262c9ad4325e
  4. 26d ago Changed · +8 lines 9bce3f1dfa0d
  5. 1mo ago Changed 7c8f22ffb0a5
  6. 1mo ago Changed · -67 lines 7eb2403fefbe
  7. 1mo ago Changed ff90e8306442
  8. 1mo ago Changed · -6 lines 6d0d84a447f0
  9. 1mo ago Changed · +2 lines e177d7d7a113
  10. 1mo ago First seen · 313 lines · 19 tokens per session scan A 6608c172feba

Subscribe to this mod's changes

gem-orchestrator is an agent published in the GitHub repository mubaidr/gem-team (227 stars, last pushed 8d ago), licensed Apache-2.0. 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. It is 92% identical to gem-orchestrator, differing in 0 lines, and is treated as a copy.

Code reviewPlanningTDDai-agentsautomationcursoropencodewindsurf
Related

Other agents, from other repositories

code-reviewer

A senior review process for proposed code changes. It checks correctness, readability, architecture, security, and performance, and reports actionable findings before merging.

vinvcn/addyosmani-agent-skills-zh · 37 tokens

spring-code-reviewer

Phase 7 — pre-commit human-style review against the full diff and validation report. Produce 08-code-review.md and final verdict; block commit on unwaived blockers.

loiane/specs-driven-development-spring-angular · 41 tokens

code-auditor

Analyzes implemented code for pattern consistency, maintainability, code duplication, comment quality, and documentation drift.

rp1-run/rp1 · 25 tokens

ipc-contract-auditor

Use when IPC or command-surface drift is possible — after adding, renaming, or removing a Tauri command, a SidecarCommand/SidecarEvent variant, or a tauri-api.ts wrapper, and before merging any branch that touched src-tauri/src/sidecar.rs, src-tauri/sidecar-opencode/src/types.ts, src-tauri/src/lib.rs, or…

kevinlin/cowork-z · 105 tokens

code-reviewer-bug

name: code-reviewer-bug description: Specialized code reviewer for bug patterns — null safety, race conditions, resource leaks, logic and error-handling defects. Returns scored findings (severity × impact × confidence). skills: code-review model: inherit.

zxpmail/ReqForge · 0 tokens

code-reviewer

Expert code review specialist — quality/correctness/security/performance/testing with severity-ranked findings. Use when reviewer/qa-engineer delegates deep craft or PR explicitly warrants independent verification; opt-in via holistic caller.

ulises-jeremias/agent-toolkit · 45 tokens