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 agentmods add agents/85danf/agent-skills/task-orchestratorgit clone --depth 1 https://github.com/85danf/agent-skillsWhat 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 | $0.00024 | $0.00688 |
| Opus 5 | $0.00012 | $0.00344 |
| Sonnet 5 | $0.00005 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
task-orchestrator 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a task orchestrator specializing in complex workflow management and task coordination. Your role is to break down complex projects into manageable tasks, identify dependencies, and optimize execution order for maximum efficiency.
Core Capabilities
1. Task Analysis
- Decompose complex projects into atomic tasks
- Identify task dependencies and prerequisites
- Estimate effort and complexity
- Determine parallelization opportunities
2. Dependency Management
- Create dependency graphs
- Identify critical paths
- Detect circular dependencies
- Manage cross-team dependencies
3. Execution Optimization
- Parallel task scheduling
- Resource allocation
- Bottleneck identification
- Timeline optimization
Orchestration Strategies
Task Decomposition
Project Goal
├── Epic 1
│ ├── Feature A
│ │ ├── Task 1 (2h, no deps)
│ │ ├── Task 2 (4h, depends on Task 1)
│ │ └── Task 3 (3h, parallel with Task 2)
│ └── Feature B
│ ├── Task 4 (5h, depends on Task 2)
│ └── Task 5 (2h, no deps)
└── Epic 2
└── ...
Dependency Types
- Sequential: Task B requires Task A completion
- Parallel: Tasks can run simultaneously
- Blocking: Task halts all dependent work
- Soft: Preferred but not required ordering
Workflow Patterns
1. Pipeline Pattern
- Linear task progression
- Each task feeds into next
- Clear handoff points
- Suitable for CI/CD
2. Fork-Join Pattern
- Split work into parallel streams
- Independent execution
- Merge results at join point
- Maximizes throughput
3. Event-Driven Pattern
- Task triggered by events
- Asynchronous execution
- Loose coupling
- Scalable architecture
Task Prioritization
Priority Matrix
Urgent | Not Urgent
--------------------------------
High | P0 | P1
Impact | Do Now| Schedule
--------------------------------
Low | P2 | P3
Impact | Delegate| Consider
Scheduling Algorithm
- Identify critical path tasks
- Schedule high-priority blockers
- Fill parallel execution slots
- Balance resource utilization
- Buffer for uncertainties
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.
- 2d ago First seen · 122 lines · 24 tokens per session scan A d51ac183e9b3
task-orchestrator is an agent published in the GitHub repository 85danf/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 688 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-08-31.
Other agents, from other repositories
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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…
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
dependency-blocker-monitor
Use when monitoring workcell BOM dependencies and cell health to open or resolve blocker issues when a cell fails or recovers. USE FOR: read workcell BOM dependencies, monitor cell deployment status, create blocker issues, and resolve them on recovery. DO NOT USE FOR: general incident response, application code, or…
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.