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 jpicklyk/task-orchestrator --skill orchestrategit clone --depth 1 https://github.com/jpicklyk/task-orchestratorWrote 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/jpicklyk/task-orchestrator/orchestrate)<a href="https://agentmods.dev/skills/jpicklyk/task-orchestrator/orchestrate"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/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/jpicklyk/task-orchestrator/orchestrate"><img src="https://agentmods.dev/badge/skills/jpicklyk/task-orchestrator/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.00032 | $0.02495 |
| Opus 5.5 | $0.00013 | $0.00998 |
| Sonnet 5.5 | $0.00006 | $0.00499 |
| Haiku 4.5 | $0.00003 | $0.00249 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate - Tier, Delegation and Dispatch
On-demand depth for sizing work and dispatching agents. Shapes are in _generated/call-shapes.md; ids below are 8-hex shorts (a full UUID is also accepted).
orchestration.mode lives under extensions.claude-code in the project config (see extensions). The tier table and the delegation model table apply when it is workflow. In schema mode the schema alone governs process, so skip the tier and model-table content; the phase-owner dispatch rules and the explicit-model rule below still apply, with the model chosen by judgment.
Tier Classification
Classify every piece of work into a tier before starting; the tier decides how much process to apply.
| Criteria | Tier | Pipeline |
|---|---|---|
| 1-2 files, known fix, no migration/new API | Direct | Orchestrator edits, tests, reviews inline |
| 3-10 files, single logical unit, clear or explorable scope | Delegated | Single subagent, separate review agent |
| 11+ files, multiple independent work streams, dependency edges | Parallel | Worktree agents, full pipeline |
Force-UP signals (bump tier regardless of file count):
- Database migration → min Delegated
- New public API surface → min Delegated
- Multiple independent work streams → Parallel
- User says "let's plan" / collaborative language → min Delegated
Force-DOWN signals:
- User says "just fix it" / "quick" → Direct (unless complexity contradicts)
- The item's type resolves to the
defaultschema, or the item is schema-free -> eligible for Direct
Tier Pipeline Summary
| Step | Direct | Delegated | Parallel |
|---|---|---|---|
| Plan mode | skip | optional | required |
| Queue notes | none required | fill per schema | fill per schema |
| Implementation | orchestrator inline, no subagent, no delegation table | single subagent | parallel worktree agents |
| Review | inline (orchestrator) | separate agent | separate agent |
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.
- yesterday Changed · +18 lines · -1 tokens per session 177f53b0d7e0
- 17d ago Changed · +8 lines d0e416deac2d
- 20d ago First seen · 97 lines · 33 tokens per session scan A cc47ce5d6e61
orchestrate is a skill published in the GitHub repository jpicklyk/task-orchestrator (209 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 2,495 once invoked, about $0.0001 per session on Opus 5.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-10-04.
Other skills, from other repositories
branch-surgery-pr-split
Split oversized or mixed-concern branches into smaller, reviewable PR stacks with safety refs, topology selection, parity audits, and merge sequencing. Use when a PR or branch is too large, difficult to review, mixed across concerns, conflict-prone, or needs to be decomposed without losing net changes.
do-it
Turn the current discussion into a task step and implement it — adds step to task file, updates spec if needed, then implements with review-fix loop.
plan-tasks
Read an existing spec and propose a task breakdown — assesses separable work streams, proposes split, creates task files linked to the spec.
draft-issue
Draft a GitHub issue based on a discussion or requirements in the current conversation.
run-task
Run pending steps, then aftertask finalization; does not close the task.
load-spec
Load a feature spec, its linked tasks, and feature-level progress and gaps.