Borrowing it
Nothing to install: this file belongs to shintaro-sprech/agent-orchestrator-template. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shintaro-sprech/agent-orchestrator-template/main/.claude/commands/task.mdgit clone --depth 1 https://github.com/shintaro-sprech/agent-orchestrator-templateWrote 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/commands/shintaro-sprech/agent-orchestrator-template/task)<a href="https://agentmods.dev/commands/shintaro-sprech/agent-orchestrator-template/task"><img src="https://agentmods.dev/badge/commands/shintaro-sprech/agent-orchestrator-template/task.svg" alt="Measured on agentmods" 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.00010 | $0.00516 |
| Opus 5 | $0.00005 | $0.00258 |
| Sonnet 5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
task 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrated Task Execution
You MUST follow the orchestrator workflow before executing this task.
Step 1: Read Orchestrator
Read .claude/agents/orchestrator.md completely to understand the orchestration logic.
Step 2: Scan Agent Pool
Scan all existing agents:
.claude/agents/pool/specialized/- Task-specific agents.claude/agents/pool/integrated/- Merged agents.claude/agents/pool/elite/- High-performing agents
For each agent found, read its definition (.md file).
Step 3: Read Skill Sheets
Read corresponding skill sheets from .claude/agents/manifests/ to understand:
- Agent capabilities
- Constraints
- Usage metrics
- Synergy hints
Step 4: Calculate Coverage
Compare task requirements against available agent capabilities:
- List required skills for this task
- Calculate match percentage for each agent
- Identify potential synergies between agents
Step 5: Decision Matrix
| Coverage Rate | Action |
|---|---|
| 90%+ | Use existing agent directly |
| 60-90% | Create integrated agent by merging sources |
| Below 60% | Create new specialized agent |
Step 6: Agent Creation (if needed)
If creating new/integrated agent:
- Use
.claude/agents/_template.mdas base - Save agent definition to appropriate
pool/subdirectory - Create skill sheet in
manifests/
Step 7: Execute Task
Execute the following task using the selected/created agent:
$ARGUMENTS
Step 8: Update Metrics
After task completion, update the agent's skill sheet in manifests/:
- Increment
usage_count - Update
success_rate - Set
last_usedto today's date - Add entry to
task_history
Step 9: Elite Promotion Check
If agent meets criteria (usage_count >= 5 AND success_rate >= 0.8):
- Move agent from current location to
pool/elite/ - Update skill sheet
tier: elite
Step 10: Report
Report:
- Agent used (name, tier, location)
- Action taken (used existing / created new / integrated)
- Coverage achieved
- Any agents created or promoted
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 · 79 lines · 10 tokens per session scan A 185e9ec72265
task is a command published in the GitHub repository shintaro-sprech/agent-orchestrator-template (124 stars, last pushed 6d ago), licensed MIT. It adds 10 tokens to every session and 516 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.