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/Amey-Thakur/AI-SKILLSWrote 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/amey-thakur/ai-skills/orchestrator-prompt)<a href="https://agentmods.dev/commands/amey-thakur/ai-skills/orchestrator-prompt"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/orchestrator-prompt/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/commands/amey-thakur/ai-skills/orchestrator-prompt"><img src="https://agentmods.dev/badge/commands/amey-thakur/ai-skills/orchestrator-prompt.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.00021 | $0.00403 |
| Opus 5 | $0.00010 | $0.00201 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
orchestrator-prompt 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 9d 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
You were invoked as a slash command. The user's input:
$ARGUMENTS
Use that input to fill this prompt's variables (take the main content, topic, or task from it; ask only if a required value is missing and not supplied), then follow the prompt exactly.
Write an orchestrator (coordinator) prompt for: {goal}
Available workers: {workers}
The orchestrator's job is to break the goal into work, delegate it, track it, and synthesize the result. Write its prompt to cover:
- Role: it coordinates, it does not do the workers' jobs itself. Its output is delegation and synthesis, not the domain work.
- Planning: how to decompose the goal into tasks matched to the right worker (see agent-task-breakdown), and how to decide what runs in parallel versus in sequence.
- Delegation: exactly what context and instructions to pass each worker (clear, self-contained tasks: a worker only knows what it is handed).
- Tracking and adaptation: how to handle worker results, including failures and low-confidence outputs (retry, reassign, escalate), and when to stop.
- Verification: how to check worker output before trusting it (workers are confidently wrong), and how to reconcile conflicting results.
- Synthesis: how to combine the workers' outputs into the final result, and what to return.
Rules: keep the orchestrator's own reasoning about coordination, not the object work (delegate the object work). Bound it: max iterations, cost/latency limits, and a clear termination condition. Build in verification of worker output, not blind trust. Front-load the coordination rules. If the goal is simple enough for one agent, the orchestrator should recognize and say that.
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.
- 9d ago First seen · 41 lines · 21 tokens per session scan A e258cc370672
orchestrator-prompt is a command published in the GitHub repository Amey-Thakur/AI-SKILLS (7 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 403 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-03.
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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.