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/dryvist/claude-code-plugins/premium-agent-orchestrationnpx skills add dryvist/claude-code-plugins --skill premium-agent-orchestrationgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/premium-agent-orchestration)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/premium-agent-orchestration"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/premium-agent-orchestration.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 | $0.00066 | $0.02639 |
| Opus 5 | $0.00033 | $0.01319 |
| Sonnet 5 | $0.00013 | $0.00528 |
| Haiku 4.5 | $0.00007 | $0.00264 |
Grade A, and why
premium-agent-orchestration 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 today.
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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premium Agent Orchestration
Treat the model running the current session as the senior decision-maker, whatever it is — the skill is model- and vendor-agnostic and applies equally to any present or future top-tier model. Spend premium reasoning only where stronger judgment changes the outcome, and route checkable labor to the cheapest capable executor.
Purpose
Use this skill to keep expensive top-tier models focused on judgment instead of labor. Preserve premium reasoning for understanding intent, choosing strategy, managing risk, resolving ambiguity, reviewing critical outputs, and giving the final answer.
Delegate work when the result can be checked from concrete evidence. Prefer the lowest-cost executor that can reliably produce that evidence.
Senior Model Owns
Keep these decisions with the premium lead (the current session's model):
- Understand the real user intent.
- Decide what matters and what is out of scope.
- Choose the architecture or approach.
- Break ambiguous work into clear parts.
- Decide task order and dependencies.
- Make tradeoffs between speed, quality, risk, and scope.
- Identify hidden risks.
- Resolve disagreement between agents.
- Review important outputs.
- Decide when the work is good enough.
- Give the final answer to the user.
Model Tiers
Each row below is a model tier — a capability role, not a specific model name. Resolve each tier against whatever models the current environment actually offers (native subagent model options, configured CLIs, local serving); never assume a specific vendor's lineup.
| Tier | Use for | Boundary |
|---|---|---|
| Local/free | File discovery, log summaries, simple scans, checklist verification, cheap summaries | Report facts and evidence; avoid product or architecture calls |
| Small/cheap cloud | Repo discovery, large-file summaries, log inspection, simple checks, edge-case scanning | Report facts, not direction |
| Mid execution | Scoped implementation, tests, medium debugging, local refactors, following existing patterns | Execute the plan; avoid changing architecture or product intent |
| Strong reasoning | Complex implementation, deep debugging, cross-module reasoning, risky review, security-sensitive reasoning | Reason deeply, but leave final authority with the premium lead |
| Premium lead | Intent, architecture, decomposition, tradeoffs, risk, disagreement, final review, synthesis | Own final decisions and user communication |
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.
- today Changed · +4 lines 664f2099a1f2
- 5d ago First seen · 255 lines · 66 tokens per session scan A 7574a98a1b07
premium-agent-orchestration is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 2,639 once invoked, about $0.0003 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
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…