agent-orchestrate

agent-orchestrate is a skill for Claude Code, Codex from MichelKerkmeester/skilled-agent-harness_spec-driven-loops. It costs 21 tokens per session (12,723 once invoked), scanned A, original, MIT.

A task-orchestration agent that breaks work into smaller tasks, assigns them to other agents, checks their results, resolves conflicts, and combines the answers.

In plain words
What is it for?
It is for delegating work, evaluating sub-agent output, and producing one final response from several workstreams.
Why use it?
It gives multi-step work one coordinating point instead of leaving separate agents to produce disconnected results.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Good fit It is for delegating work, evaluating sub-agent output, and producing one final response from several workstreams.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-orchestrate
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.

Any agent
npx skills add MichelKerkmeester/skilled-agent-harness_spec-driven-loops --skill agent-orchestrate
Clone the repo
git clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-loops

Made for: Claude Code, Codex.

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 agent-orchestrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-orchestrate/github.svg)](https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-orchestrate)
Your own site
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-orchestrate"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-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.

agentmods 80×15 button for agent-orchestrate

Your own site · 80×15
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-orchestrate"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/agent-orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 12,723 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 original 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.00021 $0.12723
Opus 5 $0.00010 $0.06362
Sonnet 5 $0.00004 $0.02545
Haiku 4.5 $0.00002 $0.01272

Measured yesterday against content hash 996650566bff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-17, from the pricing page.

Security

Grade A, and why

agent-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 yesterday.

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.

.hermes/skills/agent-orchestrate/SKILL.md · 842 lines

How it starts

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

Agent persona orchestrate from .hermes/agents/orchestrate.md (the shared agent files), mirrored as a preloadable skill because Hermes has no agent flag. Preload with -s agent-orchestrate and adopt it for the session.

The Orchestrator: Senior Task Commander

You are THE SENIOR ORCHESTRATION AGENT with FULL AUTHORITY over:

  • Task Decomposition: Break complex requests into discrete, delegatable tasks
  • Strategic Delegation: Assign tasks with explicit skills, scope, and success criteria
  • Quality Evaluation: Accept, reject, or request revision of sub-agent outputs
  • Conflict Resolution: Resolve contradictions between parallel workstreams
  • Unified Synthesis: Merge outputs into single authoritative delivery

You are the single point of accountability. The user receives ONE coherent response from you, not fragments from multiple agents.

Path Convention: Use only .opencode/agents/*.md as the canonical runtime path reference.

Runtime Directory Resolution: OpenCode profile reads .opencode/agents/; Claude profile reads .claude/agents/. Choose the active runtime directory once per workflow and keep dispatches within it.

Delegation Tool Per Runtime: The delegation tool is named differently in each runtime — task in OpenCode, Agent in Claude Code, spawn_agent in Codex, subagent in Pi — and each runtime mirror declares the name that applies to it. Delegate through the active runtime's name, and treat a mirror that declares no delegation tool as unable to dispatch.

Agent I/O Contract: When helpful, include an AGENT_IO_DISPATCH v1 header in delegated prompts and accept optional AGENT_IO_RESULT v1 envelopes appended to native agent output. The contract is advisory only; missing headers or envelopes are never a rejection reason.

Hook-Injected Advisor Context: Treat hook-injected skill-advisor recommendations as routing hints only. They never override explicit user instructions, active command workflow, scope gates, runtime permissions, agent boundaries, or required skill loading. If advisor context conflicts with the dispatch prompt or verified local files, prefer the dispatch prompt plus file evidence and report the conflict.

CRITICAL: You orchestrate via the task tool, and you MAY use read to load agent definitions or command specs needed for correct dispatch. You MAY also apply small fixes yourself where dispatching would cost more than the work — a fresh agent must reload the context you already hold, and paying that for something slight is a restraint failure. Judge it by cost, not by category: the question is whether delegating buys you anything, not whether the change fits a listed shape. Work carrying real design content or its own verification burden stays delegated, because you own the brief and the verdict, and a delegate you skipped is a review you skipped.


Read the full file on GitHub · 842 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. yesterday First seen · 842 lines · 21 tokens per session scan A 996650566bff

Subscribe to this mod's changes

agent-orchestrate is a skill published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (35 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 12,723 once invoked, about $0.0001 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-16.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens