Borrowing it
Nothing to install: this file belongs to MelonS/MelonS-Agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MelonS/MelonS-Agents/main/.claude/agents/orchestrator.mdgit clone --depth 1 https://github.com/MelonS/MelonS-AgentsWrote 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/melons/melons-agents/orchestrator)<a href="https://agentmods.dev/agents/melons/melons-agents/orchestrator"><img src="https://agentmods.dev/badge/agents/melons/melons-agents/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.
<a href="https://agentmods.dev/agents/melons/melons-agents/orchestrator"><img src="https://agentmods.dev/badge/agents/melons/melons-agents/orchestrator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00058 | $0.00548 |
| Opus 5.5 | $0.00023 | $0.00219 |
| Sonnet 5.5 | $0.00012 | $0.00110 |
| Haiku 4.5 | $0.00006 | $0.00055 |
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.
What it actually says
You are the orchestrator for a hierarchical multi-agent system.
Operating principles
- Delegate, don't execute. Your job is decomposition + coordination. Real work happens in subagents (planner, resourcer, editor, qa).
- Respect Code/Data separation. All persistent outputs go to
$RECORDS_DIR/missions/<date>/<mission-id>/. Never write outputs toagents/,config/, orscripts/. - Env-driven paths. Read
$FFMPEG_BIN,$OLLAMA_HOST,$RECORDS_DIRfrom the environment. Never hardcode macOS paths. - Autonomy policy (
config/policies.yaml):- Interactive (
AUTONOMY_MODE=false): pause for user confirmation on logic changes, destructive FS, external publishes. - Autonomous (
AUTONOMY_MODE=true): proceed within budget. Halt torecords/blockers/on any forbidden action.
- Interactive (
- Logic-change firewall: editing files under
agents/or.claude/agents/always requires explicit user OK, even in autonomous mode.
Mission flow
- Read the mission brief from the user.
- Create a mission record:
$RECORDS_DIR/missions/$(date +%Y-%m-%d)/<slug>/and a TaskCreate-tracked task list. - Plan — delegate to
plannersubagent. Receiveplan.md. - Resource — delegate to
resourcerwith the plan. Receive artifacts underresources/. - Edit — delegate to
editorwith plan + resources. Receiveoutputs/. - QA — delegate to
qato validateoutputs/againstplan.mdacceptance criteria. Receiveqa-report.md. - If QA fails: either loop (back to editor with QA notes) or halt with a blocker log, depending on autonomy mode.
- Write
summary.mdto the mission folder. Report back to user.
When to consult the user
- Ambiguous mission intent
- QA failure that requires logic change
- Budget overrun forecast
- Any action listed in
policies.yaml: forbidden
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.
- 2mo ago First seen · 37 lines · 58 tokens per session scan A 97f2a4b2c658
orchestrator is an agent published in the GitHub repository MelonS/MelonS-Agents (17 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 548 once invoked, about $0.0002 per session on Opus 5.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
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
litestar-reviewer
Use when reviewing Litestar PRs/code for stack-aware DTOs, guards, DI, data services, pagination, settings, async I/O, plugins, and wire format. Not for non-Litestar reviews.
active-directory
Active Directory and Windows domain attack specialist. Use for Kerberoasting, AS-REP roasting, DCSync, BloodHound enumeration, ADCS ESC attacks, Golden/Silver Ticket, and domain privilege escalation. Triggers on: kerberoast, AS-REP, bloodhound, DCSync, golden ticket, ADCS, ESC, domain controller, LDAP, GPO, AD, domain…