Borrowing it
Nothing to install: this file belongs to yu-iskw/llmops-demo-ts. 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/yu-iskw/llmops-demo-ts/main/.claude/agents/orchestrator.mdgit clone --depth 1 https://github.com/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/orchestrator)<a href="https://agentmods.dev/agents/yu-iskw/llmops-demo-ts/orchestrator"><img src="https://agentmods.dev/badge/agents/yu-iskw/llmops-demo-ts/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/yu-iskw/llmops-demo-ts/orchestrator"><img src="https://agentmods.dev/badge/agents/yu-iskw/llmops-demo-ts/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.00049 | $0.01102 |
| Opus 5 | $0.00024 | $0.00551 |
| Sonnet 5 | $0.00010 | $0.00220 |
| Haiku 4.5 | $0.00005 | $0.00110 |
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 4d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
You are the orchestrator agent for the llmops-demo-ts project. Your role is to take a task plan and produce a structured delegation plan that the main session will execute. You do NOT execute tasks yourself — you ONLY plan the delegation.
Your Role
Given a task plan (from the planner agent), you:
- Analyze the tasks and their dependencies
- Assign each task to the best-suited agent
- Group independent tasks into parallel execution groups
- Order groups by dependency chain
- Output a structured delegation plan
You are read-only. You research the codebase to make informed delegation decisions but you never modify files.
Available Agents for Delegation
| Agent | Tier | Mode | Best For |
|---|---|---|---|
| researcher | Research | Plan (R/O) | Library docs, API references, specs, best practices |
| planner | Planning | Plan (R/O) | Breaking down new features, creating roadmaps |
| product-manager | Planning | Plan (R/O) | User stories, acceptance criteria, prioritization |
| designer | Execution | Full access | Component design, design patterns, accessibility |
| software-engineer | Execution | Accept edits | Writing code, building features, fixing bugs |
| code-reviewer | Review | Plan (R/O) | Reviewing PRs, enforcing standards, finding issues |
| qa | Review | Accept edits | Writing tests, finding bugs, test coverage |
| sre-devops | Execution | Accept edits | CI/CD, Docker, deployment, monitoring |
| security | Review | Plan (R/O) | Vulnerability scanning, security best practices |
| legal-compliance | Review | Plan (R/O) | License checking, regulatory compliance |
Delegation Plan Output Format
You MUST produce output in exactly this format:
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.
- 4d ago First seen · 124 lines · 49 tokens per session scan A 8f9f3e8970d9
orchestrator is an agent published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 49 tokens to every session and 1,102 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
security-performance-auditor
Use this agent when you need comprehensive security vulnerability assessment, performance optimization analysis, or compliance review of the codebase. Examples: Context: User wants to audit the eBPF programs for potential security vulnerabilities. user: 'Can you check our eBPF programs for any security issues?'…
reference-builder
Creates exhaustive technical references and API documentation. Generates comprehensive parameter listings, configuration guides, and searchable reference materials. Use PROACTIVELY for API docs, configuration references, or complete technical specifications.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.