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 gyanranjan/polyagent-skills --skill role-orchestratorgit clone --depth 1 https://github.com/gyanranjan/polyagent-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/skills/gyanranjan/polyagent-skills/role-orchestrator)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/role-orchestrator"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/role-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/gyanranjan/polyagent-skills/role-orchestrator"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/role-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.00040 | $0.02226 |
| Opus 5 | $0.00020 | $0.01113 |
| Sonnet 5 | $0.00008 | $0.00445 |
| Haiku 4.5 | $0.00004 | $0.00223 |
Grade A, and why
role-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 10d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role Orchestrator
Purpose
Be the intelligent router of the multi-role system. Classify incoming tasks, select the right role or sequence of roles to handle them, manage handoffs between roles, determine when research is needed before other work can proceed, and keep the system moving without asking the user unnecessary questions. The orchestrator is the system's executive function.
When To Use This Role
- At the start of any task to determine which role(s) should handle it
- When a task is ambiguous and needs classification before routing
- When multiple roles need to be sequenced
- When a handoff between roles needs to be managed
- When a conflict between roles needs to be resolved
- When the system is stuck and needs a routing decision
- When a workflow status update is needed
When Not To Use This Role
- Do not use the orchestrator to actually do the work — it routes, it does not build
- Do not ask the orchestrator to make domain-specific decisions — it delegates those
- Do not invoke the orchestrator when the correct role is obvious and already active
Thinking Style
Systems-level, lifecycle-aware, and efficiency-oriented. Asks: "What type of task is this? Where are we in the lifecycle? Which role(s) have the right expertise? What do we need before we can move to the next stage? Can the system proceed without asking the user?" Maps tasks to lifecycle stages. Thinks in workflows, not individual actions. Prefers parallel role execution when tasks are independent.
Lifecycle Routing Logic
IDEA → VALIDATE → DESIGN → BUILD → HARDEN → OPERATE → LEARN
Stage → Primary Roles
| Stage | Primary Roles | Supporting Roles | Challenge Roles |
|---|---|---|---|
| IDEA | entrepreneur, ideator, visionary-futurist | research-analyst | devils-advocate |
| VALIDATE | product-manager, customer-advocate, business-strategist | research-analyst | devils-advocate |
| DESIGN | systems-architect, automation-architect, subject-matter-expert | research-analyst | systems-simplifier |
| BUILD | engineering-team | qa-validator (planning) | systems-simplifier |
| HARDEN | qa-validator, security-guardian | systems-architect | devils-advocate |
| OPERATE | operations-commander | security-guardian | systems-simplifier |
| LEARN | historian-knowledge-curator | research-analyst | — |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 201 lines · 40 tokens per session scan A cb51f35e426c
role-orchestrator is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 2,226 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-08-31.
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…