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 skills/ribato22/volante/orchestratenpx skills add ribato22/volante --skill orchestrategit clone --depth 1 https://github.com/ribato22/volanteWrote 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/ribato22/volante/orchestrate)<a href="https://agentmods.dev/skills/ribato22/volante/orchestrate"><img src="https://agentmods.dev/badge/skills/ribato22/volante/orchestrate.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.00080 | $0.00333 |
| Opus 5 | $0.00040 | $0.00167 |
| Sonnet 5 | $0.00016 | $0.00067 |
| Haiku 4.5 | $0.00008 | $0.00033 |
Grade A, and why
orchestrate 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 5d 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
Use this skill only for a large, multi-part goal that benefits from being decomposed into a task DAG and routed across models. For anything simple, single-step, or quick, handle it directly and do not invoke Volante.
When it genuinely applies:
- Call the
volante_runtool from thevolanteMCP server, passing the user's full goal asgoal(optionally setprefertocash_protect_quotato protect subscription quota instead of the default quality-first routing). - Volante plans a task DAG, routes each sub-task to the best predicted fit from configured metadata/evidence after hard-capability filtering, runs each one, and synthesizes a single final answer — it returns that answer plus a status/cost footer.
- Present Volante's synthesized answer to the user, and mention the cost footer it returned.
If the volante MCP server or the volante_run tool isn't available, tell the user how to install the
Volante MCP server (see the plugin README) rather than attempting the multi-model orchestration by hand.
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.
- 5d ago First seen · 26 lines · 80 tokens per session scan A d9ca3e2593d7
orchestrate is a skill published in the GitHub repository ribato22/volante (0 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 333 once invoked, about $0.0004 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 skills, from other repositories
continuum-tools-mcp
Connect MCP servers (Stdio/SSE/StreamableHTTP) to a Continuum agent, configure tool filtering, set up tool-context capture/injection (e.g. sessionid), and read run artifacts (UI widgets, structured tool data). Invoke when the user asks "connect MCP", "filesystem tool", "remote API tool", "auto-capture sessionid"…
continuum-handoffs
Build agent-to-agent transitions with Continuum's Handoff system — triage routing, history summarization modes (FULL/SUMMARY/RECENTN/HYBRID), cycle detection, depth tracking, return-to-parent. Invoke when the user asks "route customer requests to specialists", "agent that can transfer to another", "summarize history…
continuum-llm-providers
Pick the right LLM provider, configure structured outputs, control context-window compression, and use the LLMClient directly. Provider routing is by model-string prefix; LiteLLM has been removed. Also covers Smart Gateway integration for multi-provider routing. Invoke when the user asks about "switch to Claude"…
continuum-temporal
Build durable agent workflows with Temporal — sequential/parallel/loop/conditional steps, human-in-the-loop approval gates, custom workflows and activities. Invoke when the user asks "long-running workflow", "approval gate", "human in the loop", "retry on failure", "workflow survives restart", or anything…
continuum-testing
Write tests for Continuum agents — mock LLM and memory clients via the DI Container, use fakeredis for sessions, snapshot agent responses, and run pytest-asyncio. Invoke when the user asks "test my agent", "mock the LLM", "fakeredis", "container injection", "pytest", or wants their CI to validate agent behavior…
continuum-agent
Build BaseAgent instances and run them with AgentRunner — covers fields, lifecycle hooks, structured outputs, ReAct mode, instruction modifiers, and the full execution flow. Invoke when the user asks "create an agent", "configure maxturns", "add lifecycle hooks", "structured output with Pydantic", or anything around…