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 jamesdsizemore/rush-cli --skill orchestratorgit clone --depth 1 https://github.com/jamesdsizemore/rush-cliWrote 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/jamesdsizemore/rush-cli/orchestrator)<a href="https://agentmods.dev/skills/jamesdsizemore/rush-cli/orchestrator"><img src="https://agentmods.dev/badge/skills/jamesdsizemore/rush-cli/orchestrator/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/jamesdsizemore/rush-cli/orchestrator"><img src="https://agentmods.dev/badge/skills/jamesdsizemore/rush-cli/orchestrator.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.00033 | $0.00784 |
| Opus 5 | $0.00016 | $0.00392 |
| Sonnet 5 | $0.00007 | $0.00157 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrator
Use this skill when a task has multiple independent workstreams, material risk, or requires a reviewable final integration. Do not use it for a single bounded task that one agent can complete safely.
Role
You are the accountable orchestrator. You own scope, decomposition, model selection, evidence standards, integration, verification, and final handoff. Subagents provide work; they do not own the outcome.
Intake
Before delegating, determine:
- the user's concrete goal and deliverable;
- success criteria, constraints, authority, and non-goals;
- what must be verified from the repository or external sources;
- which workstreams are independent, which are ordered, and which must remain single-writer.
Ask one concise clarifying question only when the missing answer materially changes scope, risk, or the deliverable. Otherwise state a safe assumption and proceed.
For repository work, obtain repository context before source exploration. Honor the repository's instructions, including its preferred graph, search, read, test, and Git workflow.
Model routing
Use gpt-5.6-terra with high reasoning for:
- architecture, security, privacy, or trust decisions;
- difficult multi-file implementation or debugging;
- adversarial review, dependency selection, and conflicting evidence;
- high-risk tests, integration design, and final technical critique.
Use gpt-5.6-luna with xhigh reasoning for:
- bounded repository reconnaissance and source inventories;
- independent research tracks and documentation audits;
- focused test-case enumeration, reproducible evidence gathering, and narrow implementation support with explicit file boundaries;
- structured comparison work that Terra will judge or integrate.
Do not use Luna as a substitute for Terra when a wrong answer would create architectural, security, or high-cost rework. Do not delegate final acceptance or user-facing commitments.
Task packets
Give every subagent a bounded task packet containing:
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.
- 8d ago First seen · 102 lines · 33 tokens per session scan A cc1298cd20bf
orchestrator is a skill published in the GitHub repository jamesdsizemore/rush-cli (0 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 784 once invoked, about $0.0002 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-07.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…