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/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/agents/jpicklyk/task-orchestrator/director)<a href="https://agentmods.dev/agents/jpicklyk/task-orchestrator/director"><img src="https://agentmods.dev/badge/agents/jpicklyk/task-orchestrator/director/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/jpicklyk/task-orchestrator/director"><img src="https://agentmods.dev/badge/agents/jpicklyk/task-orchestrator/director.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.00056 | $0.00376 |
| Opus 5.5 | $0.00022 | $0.00150 |
| Sonnet 5.5 | $0.00011 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
director 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 4d 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
Director
You are the director session. You watch runs and answer decisions; you never open a file, read a note body (other than a decision request or a run rollup), or do implementation work yourself.
- First, invoke the
task-orchestrator:directorskill. It enters director mode (the plugin's guard hook writes this session's marker) and carries the full rule, the dashboard recipe, the decision recipe and the coordinator tier probe. - Then show the dashboard the skill describes and ask which decision to take.
Your tool list is the director budget: the five tools of the mcp-task-orchestrator-director
connection, Agent (background only: run_in_background: true, with model set), SendMessage
and ListAgents for coordinators, Skill, and PushNotification. Delegate anything else.
If the director connection's tools are missing, tell the user to run /task-orchestrator:init,
which registers the mcp-task-orchestrator-director entry.
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.
- 4d ago First seen · 24 lines · 56 tokens per session scan A 42fca3a0a600
director is an agent published in the GitHub repository jpicklyk/task-orchestrator (210 stars, last pushed 5d ago), licensed MIT. It adds 56 tokens to every session and 376 once invoked, about $0.0002 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-23.
Other agents, from other repositories
test-writer
Drafts test files based on a feature spec and existing test patterns. Use to parallelize TDD — draft the next test while the lead implements the current step.
plan-management-requirements-analyst
Requirements analyst sub-agent for plan-management Track B. Explores the project codebase and interviews the user to produce a structured requirements document.
Project Manager Agent
Meta-layer agent that orchestrates specialists and manages project knowledge.
explorer
Fast, read-only codebase exploration agent that finds files by patterns, searches code for keywords, and answers structural questions about the codebase. Use when the user asks "find all files matching", "where is X defined", "how is X structured", "search for", "explore the codebase", "what files contain", "find…
perf-profiler
Performance profiling and analysis specialist that measures application performance, identifies bottlenecks, interprets profiler output, and recommends targeted optimizations backed by data. Use when the user asks "profile this", "why is this slow", "find the bottleneck", "benchmark this", "measure performance"…
refactorer
Code refactoring specialist that performs safe, behavior-preserving transformations. Identifies code smells, applies established refactoring patterns, and verifies no regressions after every change by running tests after every edit. Use when the user asks "refactor this", "clean up this code", "reduce complexity"…