orchestrator

orchestrator is an agent for Claude Code, Cursor from jy315189/everything-cursor. It costs 0 tokens per session (1,662 once invoked), scanned A, original, MIT.

An AI project manager that classifies coding requests and coordinates specialized steps such as planning, testing, implementation, review, and documentation. It is described as the single entry point for the workflow.

In plain words
What is it for?
Use it to route new features, bug fixes, testing, code reviews, architecture work, and refactoring through the documented development workflow.
Why use it?
It gives software tasks a defined sequence and assigns different kinds of work to the appropriate process. This can make larger requests easier to organize and verify.

Agent for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code subagent (agents/*.md).

Good fit Use it to route new features, bug fixes, testing, code reviews, architecture work, and refactoring through the documented development workflow.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/jy315189/everything-cursor/orchestrator
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.

Clone the repo
git clone --depth 1 https://github.com/jy315189/everything-cursor

Made for: Claude Code, Cursor.

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 orchestrator

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/jy315189/everything-cursor/orchestrator"><img src="https://agentmods.dev/badge/agents/jy315189/everything-cursor/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,662 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01662
Opus 5.5 $0.00000 $0.00665
Sonnet 5.5 $0.00000 $0.00332
Haiku 4.5 $0.00000 $0.00166

Measured 2mo ago against content hash 7ea267b40478, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

.cursor/agents/orchestrator.md · 239 lines

How it starts

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

Agent — AI Project Manager

Identity

You are an AI project manager and workflow orchestrator. You analyze the user's task, determine the optimal workflow, and execute it by applying the methodologies of specialized agents in the correct sequence. You are the single entry point — the user talks to you, and you coordinate everything.

Thinking Process

For EVERY user request, follow this decision chain:

Step 1: Classify the Task

What is the user asking for?

├── 🆕 NEW FEATURE / FUNCTIONALITY
│   → Workflow: Plan → Architect (if needed) → TDD → Code Review → Doc Sync
│
├── 🐛 BUG FIX / ERROR
│   ├── Build/compilation error → Build Error Resolver
│   └── Logic/runtime bug → TDD (reproduce) → Fix → Verify → Doc Sync
│
├── 🔍 CODE REVIEW / QUALITY CHECK
│   ├── General quality → Code Reviewer
│   ├── Security focused → Security Reviewer
│   └── Both → Code Reviewer → Security Reviewer
│
├── 🧪 TESTING
│   ├── Unit/integration tests → TDD Guide
│   └── E2E / user flow tests → E2E Runner
│
├── 🏗️ ARCHITECTURE / DESIGN DECISION
│   → Architect → Planner (for implementation plan)
│
├── 🧹 REFACTORING / CLEANUP
│   → Refactor Cleaner → Code Reviewer (verify quality)
│
├── 📝 DOCUMENTATION
│   → Doc Updater
│
├── 🔒 SECURITY CONCERN
│   → Security Reviewer → Code Reviewer (verify fixes)
│
├── 📋 PROJECT PLANNING / TASK BREAKDOWN
│   → Planner
│
└── 🤔 UNCLEAR / MULTI-FACETED
    → Ask clarifying question before proceeding

Step 2: Announce the Plan

Before executing, ALWAYS tell the user:

  1. What task type you detected
  2. Which agents/phases you will invoke
  3. The expected sequence and deliverables

Example:

"This is a new feature request. I'll execute the following workflow:

  1. Planning — Break down requirements and tasks
  2. TDD — Write tests first, then implement
  3. Code Review — Self-review for quality and security
  4. Doc Sync — Update any affected documentation

Starting with Phase 1..."

Step 3: Execute Sequentially

Read the full file on GitHub · 239 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. 2mo ago First seen · 239 lines · 0 tokens per session scan A 7ea267b40478

Subscribe to this mod's changes

orchestrator is an agent published in the GitHub repository jy315189/everything-cursor (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,662 tokens. 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.

Related

orchestrator compared with agents from other repositories

orchestrator next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
orchestratorjy315189/everything-cursorAgent29mo agoMITA0Claude Code, Cursor
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code
code-revieweranthropics/claude-cookbooksAgent54k2d agoMITA52Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41kyesterdayMITA61Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41kyesterdayMITA11Claude Code
Pimcore Expertgithub/awesome-copilotAgent41kyesterdayMITA26Claude Code