parallel-analyze

parallel-analyze is a command for coding agents from CloudAI-X/claude-workflow-v2. It costs 25 tokens per session (1,118 once invoked), scanned A, original, MIT.

A code-review process that asks four separate agents to examine the same file or folder from architecture, security, performance, and testing viewpoints. Their findings are combined into shared recommendations.

In plain words
What is it for?
Use it to inspect code structure, security risks, speed concerns, tests, dependencies, and design choices in parallel.
Why use it?
One review can miss problems outside its main focus. Separate reviews cover different kinds of risk at the same time and bring the results together.

Command

Part of the claude-workflow-v2 plugin — 14 skills, 26 commands, 7 agents, 6 hooks shipped together

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 commands/cloudai-x/claude-workflow-v2/parallel-analyze
Clone the repo
git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2

Or install claude-workflow-v2, the plugin that ships this one along with the rest of its 14 skills, 26 commands, 7 agents, 6 hooks.

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 parallel-analyze

README.md
[![agentmods](https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/parallel-analyze.svg)](https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/parallel-analyze)
Your own site
<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/parallel-analyze"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/parallel-analyze.svg" alt="Measured on agentmods" height="20"></a>
Per session 25 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,118 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.00025 $0.01118
Opus 5 $0.00013 $0.00559
Sonnet 5 $0.00005 $0.00224
Haiku 4.5 $0.00003 $0.00112

Measured 4d ago against content hash 2cd3c0fa9a5a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

parallel-analyze 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 4d 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.

commands/parallel-analyze.md · 205 lines

How it starts

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

Parallel Multi-Perspective Analysis

Analyze $ARGUMENTS from multiple perspectives simultaneously using parallel subagents.

Process

  1. Identify Target: Parse the file or directory to analyze
  2. Spawn Perspective Agents: Launch 4 parallel subagents (one per perspective)
  3. Collect Results: Each subagent returns its analysis automatically on completion
  4. Synthesize: Merge findings into unified recommendations

Execution Pattern

CRITICAL: Launch ALL Task calls in a SINGLE message for true parallelism.

For the target, spawn 4 perspective-based subagents with run_in_background: true:

I'm launching 4 parallel analysis agents:

[Task 1]
description: "Architecture analysis"
prompt: "You are a software architect analyzing [target]. Evaluate:
- Component structure and boundaries
- Dependency patterns and coupling
- Design pattern usage
- Layering and separation of concerns
- Scalability considerations
- SOLID principle adherence

Provide findings with file:line references and improvement suggestions."
run_in_background: true

[Task 2]
description: "Security analysis"
prompt: "You are a security auditor analyzing [target]. Check for:
- OWASP Top 10 vulnerabilities
- Input validation gaps
- Authentication/authorization issues
- Hardcoded secrets or credentials
- Injection vulnerabilities (SQL, XSS, command)
- Insecure dependencies

Provide findings with severity levels (Critical/High/Medium/Low)."
run_in_background: true

[Task 3]
description: "Performance analysis"
prompt: "You are a performance engineer analyzing [target]. Look for:
- Algorithmic complexity issues (O(n²), O(n!))
- N+1 query patterns
- Memory leaks or inefficient allocations
- Blocking operations in async contexts
- Missing caching opportunities
- Unnecessary computations

Provide findings with estimated impact levels."
run_in_background: true

[Task 4]
description: "Testing analysis"
prompt: "You are a test architect analyzing [target]. Evaluate:
- Test coverage gaps
- Missing edge case tests
- Untested error paths
- Integration test opportunities
- Test code quality
- Mocking strategy effectiveness

Provide recommendations for improving test coverage."
run_in_background: true

Read the full file on GitHub · 205 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. 4d ago First seen · 205 lines · 25 tokens per session scan A 2cd3c0fa9a5a

Subscribe to this mod's changes

parallel-analyze is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 9d ago), licensed MIT. It adds 25 tokens to every session and 1,118 once invoked, about $0.0001 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.