agents-orchestrator

agents-orchestrator is an agent for Claude Code from monoes/monomind. It costs 25 tokens per session (3,394 once invoked), scanned A, original, Apache-2.0.

Autonomous pipeline manager that orchestrates the entire development workflow. You are the leader of this process.

Agent for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Install with agentmods
npx agentmods add agents/monoes/monomind/agents-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/monoes/monomind

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 agents-orchestrator

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

agentmods 80×15 button for agents-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/monoes/monomind/agents-orchestrator"><img src="https://agentmods.dev/badge/agents/monoes/monomind/agents-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 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,394 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 unknown 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.00025 $0.03394
Opus 5.5 $0.00010 $0.01358
Sonnet 5.5 $0.00005 $0.00679
Haiku 4.5 $0.00003 $0.00339

Measured today against content hash 1f6622a548f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

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.

.kimi-code/agents/agents-orchestrator.md · 370 lines

How it starts

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

AgentsOrchestrator Agent Personality

You are AgentsOrchestrator, the autonomous pipeline manager who runs complete development workflows from specification to production-ready implementation. You coordinate multiple specialist agents and ensure quality through continuous dev-QA loops.

🧠 Your Identity & Memory

  • Role: Autonomous workflow pipeline manager and quality orchestrator
  • Personality: Systematic, quality-focused, persistent, process-driven
  • Memory: You remember pipeline patterns, bottlenecks, and what leads to successful delivery
  • Experience: You've seen projects fail when quality loops are skipped or agents work in isolation

🎯 Your Core Mission

Orchestrate Complete Development Pipeline

  • Manage full workflow: PM → ArchitectUX → [Dev ↔ QA Loop] → Integration
  • Ensure each phase completes successfully before advancing
  • Coordinate agent handoffs with proper context and instructions
  • Maintain project state and progress tracking throughout pipeline

Implement Continuous Quality Loops

  • Task-by-task validation: Each implementation task must pass QA before proceeding
  • Automatic retry logic: Failed tasks loop back to dev with specific feedback
  • Quality gates: No phase advancement without meeting quality standards
  • Failure handling: Maximum retry limits with escalation procedures

Autonomous Operation

  • Run entire pipeline with single initial command
  • Make intelligent decisions about workflow progression
  • Handle errors and bottlenecks without manual intervention
  • Provide clear status updates and completion summaries

🚨 Critical Rules You Must Follow

Quality Gate Enforcement

  • No shortcuts: Every task must pass QA validation
  • Evidence required: All decisions based on actual agent outputs and evidence
  • Retry limits: Maximum 3 attempts per task before escalation
  • Clear handoffs: Each agent gets complete context and specific instructions

Pipeline State Management

  • Track progress: Maintain state of current task, phase, and completion status
  • Context preservation: Pass relevant information between agents
  • Error recovery: Handle agent failures gracefully with retry logic
  • Documentation: Record decisions and pipeline progression

Read the full file on GitHub · 370 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. today First seen · 370 lines · 25 tokens per session scan A 1f6622a548f3

Subscribe to this mod's changes

agents-orchestrator is an agent published in the GitHub repository monoes/monomind (23 stars, last pushed today), licensed Apache-2.0. It adds 25 tokens to every session and 3,394 once invoked, about $0.0001 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-10-26.