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 ericgandrade/claude-superskills --skill agent-skill-orchestratorgit clone --depth 1 https://github.com/ericgandrade/claude-superskillsWrote 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/ericgandrade/claude-superskills/agent-skill-orchestrator)<a href="https://agentmods.dev/skills/ericgandrade/claude-superskills/agent-skill-orchestrator"><img src="https://agentmods.dev/badge/skills/ericgandrade/claude-superskills/agent-skill-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/ericgandrade/claude-superskills/agent-skill-orchestrator"><img src="https://agentmods.dev/badge/skills/ericgandrade/claude-superskills/agent-skill-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.00072 | $0.04260 |
| Opus 5 | $0.00036 | $0.02130 |
| Sonnet 5 | $0.00014 | $0.00852 |
| Haiku 4.5 | $0.00007 | $0.00426 |
Grade A, and why
agent-skill-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 11d 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 — 590 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agent-skill-orchestrator
Purpose
Intelligent task planning and resource orchestration engine that analyzes user requirements and creates strategic execution plans using the best available resources. This skill performs automated discovery, intelligent matching with confidence scoring, and generates comprehensive plans with multiple options and fallback strategies.
The orchestrator operates as a planning assistant—it recommends approaches but always requests explicit user approval before execution. It serves as the intelligence layer above the discovery foundation, transforming "what do I have" into "how should I use it".
When to Use
Invoke this skill when:
- User has a complex task requiring multiple steps or resources
- User wants to know the best approach to solve a problem
- User needs coordination between multiple plugins, agents, skills, or MCPs
- User wants optimized resource utilization for a task
- User is unsure which tools or approach to use
- User needs a strategic plan before implementation
- User wants to explore multiple solution approaches
Platform Support
Works identically on all AI CLI platforms:
- Claude Code (
claude) - GitHub Copilot CLI (
gh copilot) - Gemini CLI (
gemini) - OpenCode (
opencode) - OpenAI Codex (
codex)
Progress Tracking
Display progress before each orchestration phase:
[██░░░░░░░░░░░░░░░░░░] 15% — Step 0: Discovering Available Resources
[████░░░░░░░░░░░░░░░░] 25% — Step 1: Analyzing User Request
[████████░░░░░░░░░░░░] 45% — Step 2: Intelligent Matching & Scoring
[████████████░░░░░░░░] 65% — Step 3: Generating Execution Plan
[██████████████████░░] 85% — Step 4: Presenting Plan for Approval
[████████████████████] 100% — Step 5: Plan Approved / Execution Ready
Workflow
Step -1: Prompt Quality Check (Pre-Analysis)
Objective: Ensure user request is clear and well-structured before planning.
Why This Step Matters:
- Vague prompts → poor resource matching → low-quality plans
- Optimized prompts → precise requirements → high-confidence plans
- Reduces planning iterations and "Refine plan" cycles
What ships with it
3 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.
- 11d ago First seen · 590 lines · 72 tokens per session scan A cc8555e09d74
agent-skill-orchestrator is a skill published in the GitHub repository ericgandrade/claude-superskills (75 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 4,260 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-30.
Other skills, from other repositories
writing-fragments
Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions "fragments", "ideate"…
obsidian-vault
Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.
continuous-learning-v2
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
review
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…
writing-shape
Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants…