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/skills/orchestrate/SKILL.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/skills/yu-iskw/llmops-demo-ts/orchestrate)<a href="https://agentmods.dev/skills/yu-iskw/llmops-demo-ts/orchestrate"><img src="https://agentmods.dev/badge/skills/yu-iskw/llmops-demo-ts/orchestrate/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/skills/yu-iskw/llmops-demo-ts/orchestrate"><img src="https://agentmods.dev/badge/skills/yu-iskw/llmops-demo-ts/orchestrate.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.00053 | $0.00451 |
| Opus 5 | $0.00026 | $0.00226 |
| Sonnet 5 | $0.00011 | $0.00090 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
orchestrate 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 5d 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
Orchestrate
Produce a structured delegation plan for the following:
$ARGUMENTS
Instructions
- Read the input: If a task plan is provided, analyze its tasks and dependencies. If only a description is provided, first break down the work, then plan delegation.
- Research the codebase: Explore relevant files to understand what agents will need to work with.
- Assign agents: Match each task to the best-suited agent based on expertise.
- Group for parallelism: Identify which tasks can run in parallel (no shared file edits, no dependencies between them).
- Order by dependencies: Tasks that depend on others go in later groups.
- Output the delegation plan: Use the structured format below.
Output Format
## Delegation Plan
### Overview
[One sentence summary]
### Parallel Group 1: [Name]
Dependencies: none
| Task | Agent | Description | Files |
|------|-------|-------------|-------|
| 1.1 | [agent-name] | [What to do] | [Which files] |
### Parallel Group 2: [Name]
Dependencies: Group 1
| Task | Agent | Description | Files |
|------|-------|-------------|-------|
| 2.1 | [agent-name] | [What to do] | [Which files] |
### Quality Gates
- [ ] [What must pass]
Rules
- NEVER execute tasks — only plan the delegation
- Maximize parallelism by grouping independent tasks
- Never assign two agents to edit the same file in the same parallel group
- Always schedule review agents (code-reviewer, qa, security) after implementation agents
- Be specific about which files each agent should work with
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.
- 5d ago First seen · 57 lines · 53 tokens per session scan A 89ad354429bc
orchestrate is a skill published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 53 tokens to every session and 451 once invoked, about $0.0003 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 skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
meta-meeting-to-workflow
Use this meta-skill instead of answering directly when the user has meeting notes, transcripts, recordings, or rough discussion notes and wants them converted into decisions, owners, follow-ups, tasks, issues, or shareable minutes through multi-skill orchestration.
meta-github-pr-watch-digest
Inspect the user's open GitHub PRs / failing CI / new issues via gh, summarize into 3 buckets (to-review / awaiting-me / CI-red), and persist follow-ups to memory.
meta-issue-to-pr-autopilot
Triages an issue, delegates the fix to sub-agent, drafts a PR description with summarize, and opens the PR via gh. Best used on small, well-scoped issues with clear acceptance criteria.
secretary
Workspace and research management — dispatch analyses, monitor running agents, manage workspaces and threads.
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.