aistack-orchestrate

aistack-orchestrate is a skill for Claude Code from blackms/aistack. It costs 96 tokens per session (748 once invoked), scanned A, original, MIT.

A workflow for splitting a large coding task among specialised AI agents, such as programmers, testers, reviewers and security auditors. It coordinates their work and handoffs through aistack.

In plain words
What is it for?
Use it to plan multi-agent coding workflows, assign parts of a task to the right agent, and pass results between agents. It is intended for larger tasks rather than small, single-step changes.
Why use it?
It avoids making one general-purpose agent handle unrelated kinds of work. It is useful when a task benefits from separate design, implementation, testing or review stages.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code.

Part of the aistack plugin — 3 skills, 3 commands shipped together

Good fit Use it to plan multi-agent coding workflows, assign parts of a task to the right agent, and pass results between agents. It is intended for larger tasks rather than small, single-step changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/blackms/aistack/orchestrate
Install

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.

Any agent
npx skills add blackms/aistack --skill orchestrate
Clone the repo
git clone --depth 1 https://github.com/blackms/aistack

Made for: Claude Code.

Or install aistack, the plugin that ships this one along with the rest of its 3 skills, 3 commands.

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 aistack-orchestrate

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/blackms/aistack/orchestrate"><img src="https://agentmods.dev/badge/skills/blackms/aistack/orchestrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 748 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.00096 $0.00748
Opus 5.5 $0.00038 $0.00299
Sonnet 5.5 $0.00019 $0.00150
Haiku 4.5 $0.00010 $0.00075

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

Security

Grade A, and why

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

plugin/skills/orchestrate/SKILL.md · 50 lines

How it starts

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

aistack: Orchestrate a multi-agent run

aistack turns Claude Code into a multi-agent orchestrator. Instead of one generalist doing everything, you decompose work and route each part to a specialized agent backed by the bundled aistack MCP server.

When to use

  • A task spans distinct skills (design + implement + test + review).
  • You want a dedicated critic (adversarial / reviewer) separate from the implementer.
  • The user explicitly asks to orchestrate, spawn agents, or run a workflow.

For a small, single-step change, do not orchestrate — just do it directly.

Available agent types

Type Best at Default model
coder Implement / refactor / debug sonnet
architect System design, trade-offs opus
reviewer Code review against conventions sonnet
adversarial Break the change, find defects opus
tester Write and run tests sonnet
researcher Investigate, gather sources sonnet
security-auditor OWASP-style security review opus
analyst Data / metrics analysis sonnet
devops CI/CD, infra, containers sonnet
documentation Docs and references sonnet
coordinator Plan and route across agents opus
grader Score outcomes against a rubric sonnet

How to orchestrate

  1. Decompose: break the task into 1–4 sub-tasks, each mapped to one agent type above.
  2. Discover tools: the aistack MCP server exposes agent_types, agent_spawn, agent_list, agent_status, agent_stop, task_create, task_assign. List them with npx @blackms/aistack mcp tools if unsure.
  3. Spawn: call agent_spawn with the chosen type and a focused prompt (include acceptance criteria and the relevant file paths). Spawn background where possible so you can fan out.
  4. Coordinate: track progress with agent_list / agent_status. Pass artifacts between agents via shared memory (see the aistack-memory skill) rather than re-deriving them.
  5. Converge: when sub-tasks finish, have a reviewer or adversarial agent validate the combined result before reporting back.

Read the full file on GitHub · 50 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 First seen · 50 lines · 96 tokens per session scan A 12fc1fb5e30f

Subscribe to this mod's changes

aistack-orchestrate is a skill published in the GitHub repository blackms/aistack (53 stars, last pushed 5mo ago), licensed MIT. It adds 96 tokens to every session and 748 once invoked, about $0.0004 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-30.

Related

aistack-orchestrate compared with skills from other repositories

aistack-orchestrate next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
aistack-orchestrateblackms/aistackSkill535mo agoMITA96Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k2d agoMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100k2d agoApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394kyesterdayMITA36Claude Code
systematic-debuggingobra/superpowersSkill315k5d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code