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.
npx skills add MichelKerkmeester/skilled-agent-harness_spec-driven-loops --skill hermes_skills_agent-orchestrategit clone --depth 1 https://github.com/MichelKerkmeester/skilled-agent-harness_spec-driven-loopsWrote 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/michelkerkmeester/skilled-agent-harness_spec-driven-loops/hermes_skills_agent-orchestrate)<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/hermes_skills_agent-orchestrate"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/hermes_skills_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.
<a href="https://agentmods.dev/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/hermes_skills_agent-orchestrate"><img src="https://agentmods.dev/badge/skills/michelkerkmeester/skilled-agent-harness_spec-driven-loops/hermes_skills_agent-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.00021 | $0.12926 |
| Opus 5.5 | $0.00008 | $0.05170 |
| Sonnet 5.5 | $0.00004 | $0.02585 |
| Haiku 4.5 | $0.00002 | $0.01293 |
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 6d 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.
This is a copy
91% identical to agent-orchestrate — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 846 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent persona
orchestratefrom.hermes/agents/orchestrate.md(the shared agent files), mirrored as a preloadable skill because Hermes has no agent flag. Preload with-s agent-orchestrateand 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 .skilled/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.
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.
- 6d ago First seen · 846 lines · 21 tokens per session scan A 3bb517d1e329
agent-orchestrate is a skill published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (37 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 12,926 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to agent-orchestrate, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…