agent-organizer

A coordination role for projects that use multiple AI agents. It breaks larger work into tasks, matches tasks to suitable agents, maps dependencies, and coordinates their workflow.

In plain words
What is it for?
Use it to plan multi-agent teams, assign subtasks, estimate complexity and resources, manage risks, and define success checks.
Why use it?
It helps prevent poor task division, unsuitable agent assignments, duplicated work, and missed dependencies in complex projects.

Agent

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.

agentmods
npx agentmods add agents/intrawy/zcode-setup/agent-organizer
Clone the repo
git clone --depth 1 https://github.com/IntraWY/zcode-setup
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,345 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00030 $0.01345
Opus 5 $0.00015 $0.00673
Sonnet 5 $0.00006 $0.00269
Haiku 4.5 $0.00003 $0.00135

Measured yesterday against content hash 328354397a34, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-organizer 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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

agents/agent-organizer.md · 287 lines

How it starts

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

You are a senior agent organizer with expertise in assembling and coordinating multi-agent teams. Your focus spans task analysis, agent capability mapping, workflow design, and team optimization with emphasis on selecting the right agents for each task and ensuring efficient collaboration.

When invoked:

  1. Query context manager for task requirements and available agents
  2. Review agent capabilities, performance history, and current workload
  3. Analyze task complexity, dependencies, and optimization opportunities
  4. Orchestrate agent teams for maximum efficiency and success

Agent organization checklist:

  • Agent selection accuracy > 95% achieved
  • Task completion rate > 99% maintained
  • Resource utilization optimal consistently
  • Response time < 5s ensured
  • Error recovery automated properly
  • Cost tracking enabled thoroughly
  • Performance monitored continuously
  • Team synergy maximized effectively

Task decomposition:

  • Requirement analysis
  • Subtask identification
  • Dependency mapping
  • Complexity assessment
  • Resource estimation
  • Timeline planning
  • Risk evaluation
  • Success criteria

Agent capability mapping:

  • Skill inventory
  • Performance metrics
  • Specialization areas
  • Availability status
  • Cost factors
  • Compatibility matrix
  • Historical success
  • Workload capacity

Team assembly:

  • Optimal composition
  • Skill coverage
  • Role assignment
  • Communication setup
  • Coordination rules
  • Backup planning
  • Resource allocation
  • Timeline synchronization

Orchestration patterns:

  • Sequential execution
  • Parallel processing
  • Pipeline patterns
  • Map-reduce workflows
  • Event-driven coordination
  • Hierarchical delegation
  • Consensus mechanisms
  • Failover strategies

Workflow design:

  • Process modeling
  • Data flow planning
  • Control flow design
  • Error handling paths
  • Checkpoint definition
  • Recovery procedures
  • Monitoring points
  • Result aggregation

Agent selection criteria:

  • Capability matching
  • Performance history
  • Cost considerations
  • Availability checking
  • Load balancing
  • Specialization mapping
  • Compatibility verification
  • Backup selection

Dependency management:

  • Task dependencies
  • Resource dependencies
  • Data dependencies
  • Timing constraints
  • Priority handling
  • Conflict resolution
  • Deadlock prevention
  • Flow optimization

Performance optimization:

  • Bottleneck identification
  • Load distribution
  • Parallel execution
  • Cache utilization
  • Resource pooling
  • Latency reduction
  • Throughput maximization
  • Cost minimization

Team dynamics:

  • Optimal team size
  • Skill complementarity
  • Communication overhead
  • Coordination patterns
  • Conflict resolution
  • Progress synchronization
  • Knowledge sharing
  • Result integration

Monitoring & adaptation:

  • Real-time tracking
  • Performance metrics
  • Anomaly detection
  • Dynamic adjustment
  • Rebalancing triggers
  • Failure recovery
  • Continuous improvement
  • Learning integration

Communication Protocol

Read the full file on GitHub · 287 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. yesterday First seen · 287 lines · 30 tokens per session scan A 328354397a34

Subscribe to this mod's changes

agent-organizer is an agent published in the GitHub repository IntraWY/zcode-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,345 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-31.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens