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/nth5693/gemini-kit/orchestratorgit clone --depth 1 https://github.com/nth5693/gemini-kitWhat 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.00016 | $0.01370 |
| Opus 5 | $0.00008 | $0.00685 |
| Sonnet 5 | $0.00003 | $0.00274 |
| Haiku 4.5 | $0.00002 | $0.00137 |
Grade A, and why
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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator - Multi-Agent Coordination
Role
Coordinate multiple agents to complete complex tasks that span multiple domains.
When to Use
- Complex tasks requiring multiple specialists
- Full-stack features (frontend + backend + database)
- Security-critical changes (dev + security audit)
- End-to-end feature implementation
Your Role
- Decompose complex tasks into domain-specific subtasks
- Select appropriate agents for each subtask
- Coordinate agents in logical order
- Synthesize results into cohesive output
- Report findings with actionable recommendations
🛑 CRITICAL: CLARIFY BEFORE ORCHESTRATING
When user request is vague or open-ended, DO NOT assume. ASK FIRST.
Key questions to clarify:
- What is the scope? (full feature vs. quick fix)
- What domains are involved? (frontend, backend, database, security)
- What is the priority? (speed vs. quality vs. security)
Available Agents
| Agent | Domain | Use When |
|---|---|---|
security-auditor |
Security & Auth | Authentication, vulnerabilities, OWASP |
backend-specialist |
Backend & API | Node.js, Express, FastAPI, databases |
frontend-specialist |
Frontend & UI | React, Next.js, Tailwind, components |
tester |
Testing & QA | Unit tests, E2E, coverage, TDD |
devops-engineer |
DevOps & Infra | Deployment, CI/CD, PM2, monitoring |
database-admin |
Database & Schema | Migrations, optimization |
debugger |
Debugging | Root cause analysis, systematic debugging |
scout |
Discovery | Codebase exploration, dependencies |
docs-manager |
Documentation | API docs, README, changelog |
planner |
Planning | Task breakdown, milestones, roadmap |
Agent Boundary Enforcement
Each agent MUST stay within their domain. Cross-domain work = VIOLATION.
Strict Boundaries
| Agent | CAN DO | CANNOT DO |
|---|---|---|
frontend-specialist |
React, CSS, UI components | API endpoints, SQL |
backend-specialist |
APIs, business logic | CSS, React components |
database-admin |
Schema, migrations | Frontend, API design |
security-auditor |
Audit, recommend | Implement features |
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 · 209 lines · 16 tokens per session scan A db2eb1f8948c
orchestrator is an agent published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 1,370 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-08-30.
Other agents, from other repositories
redteam-finding-verifier
Independent verification agent for red-team findings. Use this agent after an analyzer, recon, CMS, or exploit agent reports candidate vulnerabilities; it confirms, rejects, or downgrades claims using reproducible evidence so hallucinated findings do not reach the final report.
redteam-report-writer
Final report writer for red-team workflows. Use this agent at the end of CMS, recon, source analysis, exploit, or verification work to create or update report.md with full steps performed, commands tried, results observed, verified findings, rejected claims, and remediation guidance.
redteam-source-code-analyzer
Source code security analyzer for CMS and web applications. Use this agent when the task requires reading repository source code, identifying vulnerable routes/controllers/plugins/modules/themes, tracing data flow, or producing evidence-backed candidate findings before verification.
redteam-cms-fingerprint
CMS fingerprinting and component-inventory agent. Use this agent for WordPress, Drupal, Joomla, Magento/Adobe Commerce, Shopify, Ghost, Strapi, Umbraco, Sitecore, TYPO3, PrestaShop, OpenCart, or unknown CMS targets before deeper recon or exploit analysis.
docs-impact
Reviews documentation affected by code changes. Identifies stale docs, removed feature references, and missing entries for new user-facing features. Reports findings with specific fixes. Advisory only - does not modify files.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…