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.
git 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/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/orchestrate)<a href="https://agentmods.dev/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/orchestrate"><img src="https://agentmods.dev/badge/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/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/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/orchestrate"><img src="https://agentmods.dev/badge/agents/michelkerkmeester/skilled-agent-harness_spec-driven-loops/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.00020 | $0.12592 |
| Opus 5 | $0.00010 | $0.06296 |
| Sonnet 5 | $0.00004 | $0.02518 |
| Haiku 4.5 | $0.00002 | $0.01259 |
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 3d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- orchestrate — 94% identical, 66 lines differ
How it starts
The opening of the file, as written. The whole thing — 837 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 .claude/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.
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.
- 3d ago Changed · -2 lines 02028cb996f0
- 5d ago Changed · +20 lines 97ad7eab366a
- 7d ago First seen · 819 lines · 20 tokens per session scan A 4a4ac1cb660f
orchestrate is an agent published in the GitHub repository MichelKerkmeester/skilled-agent-harness_spec-driven-loops (35 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 12,592 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-01.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…