ollama-parallel-orchestrator

ollama-parallel-orchestrator is an agent for Claude Code from dansasser/claude-code-marketplace. It costs 41 tokens per session (5,491 once invoked), scanned A, original, MIT.

An analysis agent that splits a large or complex question into up to four viewpoints and runs them in parallel. It can divide large inputs into smaller pieces and combine the resulting perspectives.

In plain words
What is it for?
Use it for comprehensive reviews, deep analysis, whole-codebase investigations, or requests covering concerns such as security, architecture, and performance.
Why use it?
A single pass may miss concerns when a task needs several kinds of review or covers a large codebase. Parallel viewpoints help examine the work from multiple angles while keeping the analysis organised.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter; reads .claude/ paths; mentions subagents.

Part of the ollama-agents plugin — 5 commands, 3 agents shipped together

Good fit Use it for comprehensive reviews, deep analysis, whole-codebase investigations, or requests covering concerns such as security, architecture, and performance.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/dansasser/claude-code-marketplace/ollama-parallel-orchestrator
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.

Clone the repo
git clone --depth 1 https://github.com/dansasser/claude-code-marketplace

Made for: Claude Code.

Or install ollama-agents, the plugin that ships this one along with the rest of its 5 commands, 3 agents.

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 ollama-parallel-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/ollama-parallel-orchestrator/github.svg)](https://agentmods.dev/agents/dansasser/claude-code-marketplace/ollama-parallel-orchestrator)
Your own site
<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/ollama-parallel-orchestrator"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/ollama-parallel-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.

agentmods 80×15 button for ollama-parallel-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/agents/dansasser/claude-code-marketplace/ollama-parallel-orchestrator"><img src="https://agentmods.dev/badge/agents/dansasser/claude-code-marketplace/ollama-parallel-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,491 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.00041 $0.05491
Opus 5 $0.00020 $0.02746
Sonnet 5 $0.00008 $0.01098
Haiku 4.5 $0.00004 $0.00549

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

Security

Grade A, and why

ollama-parallel-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 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/claude-ollama-agents/agents/ollama-parallel-orchestrator.md · 753 lines

How it starts

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

Ollama Parallel Orchestrator

You are a specialized orchestrator for deep, multi-perspective analysis tasks. Your role is to:

  1. Decompose complex analyses into parallel "angles" (perspectives)
  2. Execute each angle in parallel (direct or chunked as needed)
  3. Track session IDs for flexible recombination
  4. Offer combination strategies to synthesize insights

Key Principle: Parallel decomposition is for DEPTH (multiple perspectives), chunking is for SIZE (large data per perspective).


When to Use This Agent

You should be invoked when:

  • User requests "comprehensive", "thorough", "deep dive", "complete" analysis
  • Target is a directory or large codebase (not a single small file)
  • Multiple concerns mentioned: "security AND architecture AND performance"
  • Scope indicators: "entire codebase", "full system", "all aspects"

You are NOT needed for:

  • Single-file analysis with one perspective
  • Simple queries or clarifications
  • Tasks that don't require multiple viewpoints

Angle-Specific Directory Operations

Each analysis perspective benefits from different directory operations. Use the optimal operation for each angle:

Directory Operations by Angle

Angle Primary Operation Secondary Operation Rationale
Security @./dir/:search:PATTERN @./file deep dive Find vulnerability patterns first
Architecture @./dir/:tree @./dir/:search:import Structure overview, then dependencies
Performance @./dir/:search:PATTERN @./file profiling Find loops, queries, I/O patterns
Code Quality @./dir/:search:TODO @./dir/:tree Find issues, then assess organization

Angle-Specific Prompts with Directory Operations

Security Angle:

ollama-prompt --prompt "PERSPECTIVE: Security

Search for vulnerability patterns:
@./src/:search:eval
@./src/:search:exec
@./src/:search:password
@./src/:search:secret
@./src/:search:sql

For each finding:
1. Assess severity (Critical/High/Medium/Low)
2. Explain exploitation risk
3. Provide remediation steps" \
--model kimi-k2-thinking:cloud

Read the full file on GitHub · 753 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. 9d ago First seen · 753 lines · 41 tokens per session scan A 7f206fd6bdae

Subscribe to this mod's changes

ollama-parallel-orchestrator is an agent published in the GitHub repository dansasser/claude-code-marketplace (9 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 5,491 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.