orchestrating-multi-agents

orchestrating-multi-agents is a skill for Claude Code, Codex from J-Pster/Psters_AI_Workflow. It costs 32 tokens per session (278 once invoked), scanned A, original, MIT.

A workflow for coordinating several AI helpers on separate parts of a larger task. It assigns each helper a clear responsibility and combines their findings through one final owner.

In plain words
What is it for?
It helps split independent research or review tasks into parallel workstreams, collect concise results, resolve disagreements, and produce one merged plan or report.
Why use it?
It helps handle broad work faster and with more focused review while reducing duplicated effort and conflicting changes.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit It helps split independent research or review tasks into parallel workstreams, collect concise results, resolve disagreements, and produce one merged plan or report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/j-pster/psters_ai_workflow/orchestrating-multi-agents
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 J-Pster/Psters_AI_Workflow --skill orchestrating-multi-agents
Clone the repo
git clone --depth 1 https://github.com/J-Pster/Psters_AI_Workflow

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 orchestrating-multi-agents

README.md
[![agentmods](https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/orchestrating-multi-agents/github.svg)](https://agentmods.dev/skills/j-pster/psters_ai_workflow/orchestrating-multi-agents)
Your own site
<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/orchestrating-multi-agents"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/orchestrating-multi-agents/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 orchestrating-multi-agents

Your own site · 80×15
<a href="https://agentmods.dev/skills/j-pster/psters_ai_workflow/orchestrating-multi-agents"><img src="https://agentmods.dev/badge/skills/j-pster/psters_ai_workflow/orchestrating-multi-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 278 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.00032 $0.00278
Opus 5 $0.00016 $0.00139
Sonnet 5 $0.00006 $0.00056
Haiku 4.5 $0.00003 $0.00028

Measured 9d ago against content hash d213d037e744, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

orchestrating-multi-agents 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 9d 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.

plugins/psters-ai-workflow/skills/orchestrating-multi-agents/SKILL.md · 44 lines

What it actually says

Orchestrating Multi-Agents

Use this skill when a task benefits from parallel specialist analysis or implementation.

When to use

  • Independent research tracks (architecture, security, performance)
  • Cross-repo impact analysis
  • Large review surfaces requiring specialized reviewers
  • Structured synthesis from multiple viewpoints

Guardrails

  1. Keep one orchestrator owner for final merge.
  2. Split tasks by clear responsibility boundaries.
  3. Run only independent tasks in parallel.
  4. Merge into one deterministic decision/report.
  5. For high-risk autonomous actions, ask user before execution.

Execution pattern

  1. Define 2-4 parallel lanes with explicit deliverables.
  2. Launch subagents simultaneously.
  3. Require concise, structured outputs from each lane.
  4. Resolve conflicts explicitly (do not average contradictions).
  5. Produce final plan/report with rationale and chosen direction.

Naming convention

In prompts, reference agents with collision-safe namespace:

  • psters-ai-workflow:<category>:<agent-name>

Anti-patterns

  • Parallelizing dependent tasks that need sequencing
  • Letting subagents mutate broad code areas without clear ownership
  • Returning multiple conflicting answers without a final merged decision
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. 9d ago First seen · 44 lines · 32 tokens per session scan A d213d037e744

Subscribe to this mod's changes

orchestrating-multi-agents is a skill published in the GitHub repository J-Pster/Psters_AI_Workflow (289 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 278 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-30.