Skills-Agent: Skill for Claude Code

.agent/skills/orchestrate/SKILL.md

orchestrate is a skill for Claude Code, Codex from VoTruongDanh/Skills-Agent. It costs 57 tokens per session (909 once invoked), scanned A, original, MIT.

A coordination skill for breaking a complex request into smaller workstreams and assigning them to suitable specialist agents.

In plain words
What is it for?
Use it to plan and coordinate full-stack work, multi-step changes, or projects involving several specialist roles.
Why use it?
It helps manage tasks that span several areas, files, systems, or parallel efforts without losing track of dependencies and blockers.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

This is VoTruongDanh/Skills-Agent's own configuration. It tells Claude Code and Codex how to work on Skills-Agent itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Skills-Agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to VoTruongDanh/Skills-Agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/VoTruongDanh/Skills-Agent/main/.agent/skills/orchestrate/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/VoTruongDanh/Skills-Agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for orchestrate

README.md
[![agentmods](https://agentmods.dev/badge/skills/votruongdanh/skills-agent/orchestrate/github.svg)](https://agentmods.dev/skills/votruongdanh/skills-agent/orchestrate)
Your own site
<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/orchestrate"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/orchestrate/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.

agentmods 80×15 button for orchestrate

Your own site · 80×15
<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/orchestrate"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 909 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00909
Opus 5.5 $0.00023 $0.00364
Sonnet 5.5 $0.00011 $0.00182
Haiku 4.5 $0.00006 $0.00091

Measured 2mo ago against content hash ee75a56f3d7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.agent/skills/orchestrate/SKILL.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Protocol

START: Read .ai-memory.md from project root. Check project architecture, team structure, past orchestration plans, ongoing tasks, and blockers. END: Update .ai-memory.md using Memory Compaction Rules with: workstreams, assignments, dependencies, execution order, and blockers/risks.

Goal

Break a complex request into a coordinated execution plan with clear agent assignments.

Agent Routing

  • Primary coordinator → read .kiro/skills/agents/agents/orchestrator.md and apply its knowledge
  • For planning phases → read .kiro/skills/agents/agents/project-planner.md and apply its knowledge
  • For each workstream, read the most relevant agent file:
    • Frontend tasks → read .kiro/skills/agents/agents/frontend-specialist.md
    • Backend tasks → read .kiro/skills/agents/agents/backend-specialist.md
    • Database tasks → read .kiro/skills/agents/agents/database-architect.md
    • Testing → read .kiro/skills/agents/agents/test-engineer.md
    • Security review → read .kiro/skills/agents/agents/security-auditor.md
    • Deployment → read .kiro/skills/agents/agents/devops-engineer.md

Socratic Gate

Before orchestrating, verify:

  1. What is the full objective? (end-to-end scope)
  2. How many domains are involved? (frontend, backend, DB, infra?)
  3. Are there hard dependencies or deadlines? If any answer is unclear, ASK before proceeding.

Workflow

  1. Read Memory — Load .ai-memory.md for project context and history.
  2. Decompose the objective into workstreams.
  3. Assign each workstream to the appropriate agent/role.
  4. Identify dependencies, blockers, and the critical path.
  5. Define parallelizable tasks and merge points.
  6. Produce an execution order with clear handoffs.
  7. Quality Gate — Read .kiro/skills/_scripts/checklist.md and verify each workstream output before merge.
  8. Update Memory — Save orchestration plan to .ai-memory.md.

Output format

  • Objective
  • Workstreams (with assigned agents)
  • Dependencies and critical path
  • Execution order (sequential + parallel)
  • Risks and mitigations
  • Done criteria for each workstream

Read the full file on GitHub · 81 lines

Changes

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.

  1. 2mo ago Changed · +3 lines ee75a56f3d7f
  2. 2mo ago First seen · 78 lines · 57 tokens per session scan A f0c77b619701

Subscribe to this mod's changes

orchestrate is a skill published in the GitHub repository VoTruongDanh/Skills-Agent (4 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 909 once invoked, about $0.0002 per session on Opus 5.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.

Related

orchestrate compared with skills from other repositories

orchestrate next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
orchestrateVoTruongDanh/Skills-AgentSkill41mo agoMITA57Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code