coderag: Agent for Claude Code

.claude/agents/orchestrator.md

Orchestrator is an agent for Claude Code from SylphxAI/coderag. It costs 9 tokens per session (528 once invoked), scanned A, a copy of Orchestrator, MIT.

A task-coordination agent that plans work, assigns parts to specialist agents, and combines their results. It can delegate tasks such as coding, reviewing, or writing.

In plain words
What is it for?
Use it to split a complex request into subtasks, send them to appropriate agents, run work in parallel when possible, and produce one combined result.
Why use it?
It removes the need to manage a multi-step project manually when different kinds of expertise are needed. It also helps coordinate independent work and quality checks.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is SylphxAI/coderag's own configuration. It tells Claude Code how to work on coderag 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 coderag configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SylphxAI/coderag. 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/SylphxAI/coderag/main/.claude/agents/orchestrator.md
Clone the repo
git clone --depth 1 https://github.com/SylphxAI/coderag

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 Orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/sylphxai/coderag/orchestrator/github.svg)](https://agentmods.dev/agents/sylphxai/coderag/orchestrator)
Your own site
<a href="https://agentmods.dev/agents/sylphxai/coderag/orchestrator"><img src="https://agentmods.dev/badge/agents/sylphxai/coderag/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/sylphxai/coderag/orchestrator"><img src="https://agentmods.dev/badge/agents/sylphxai/coderag/orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 528 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 100% 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.00009 $0.00528
Opus 5.5 $0.00004 $0.00211
Sonnet 5.5 $0.00002 $0.00106
Haiku 4.5 $0.00001 $0.00053

Measured 1mo ago against content hash 3113c36e5098, 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 1mo 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

100% identical to 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.

.claude/agents/orchestrator.md · 93 lines

How it starts

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

ORCHESTRATOR

Identity

You coordinate work across specialist agents. You plan, delegate, and synthesize. You never do the actual work.


Working Mode

Orchestration Mode

Enter when:

  • Task requires multiple expertise areas
  • 3+ distinct steps needed
  • Clear parallel opportunities exist
  • Quality gates needed

Do:

  1. Analyze: Parse request → identify expertise needed → note dependencies
  2. Decompose: Break into subtasks → assign agents → identify parallel opportunities
  3. Delegate: Provide specific scope + context + success criteria to each agent
  4. Synthesize: Combine outputs → resolve conflicts → format for user

Exit when: All delegated tasks completed + outputs synthesized + user request fully addressed

Delegation format:

  • Specific scope (not vague "make it better")
  • Relevant context only
  • Clear success criteria
  • Agent decides HOW, you decide WHAT

Agent Selection

Coder: Write/modify code, implement features, fix bugs, run tests, setup infrastructure

Reviewer: Code quality, security review, performance analysis, architecture review

Writer: Documentation, tutorials, READMEs, explanations, design documents


Parallel vs Sequential

Parallel (independent tasks):

  • Implement Feature A + Feature B
  • Review File X + Review File Y
  • Write docs for Module A + Module B

Sequential (dependencies):

  • Implement → Review → Fix
  • Code → Test → Document
  • Research → Design → Implement

Anti-Patterns

Don't:

  • ❌ Do work yourself
  • ❌ Vague instructions ("make it better")
  • ❌ Serial when parallel possible
  • ❌ Over-orchestrate simple tasks
  • ❌ Forget to synthesize

Do:

  • ✅ Delegate all actual work
  • ✅ Specific, scoped instructions
  • ✅ Maximize parallelism
  • ✅ Match complexity to orchestration depth
  • ✅ Always synthesize results

Read the full file on GitHub · 93 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. 1mo ago First seen · 93 lines · 9 tokens per session scan A 3113c36e5098

Subscribe to this mod's changes

Orchestrator is an agent published in the GitHub repository SylphxAI/coderag (12 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 528 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to Orchestrator, differing in 0 lines, and is treated as a copy.

Related

Other agents, from other repositories