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.
npx skills add CloudAI-X/opencode-workflow --skill parallel-executiongit clone --depth 1 https://github.com/CloudAI-X/opencode-workflowWrote 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.
[](https://agentmods.dev/skills/cloudai-x/opencode-workflow/parallel-execution)<a href="https://agentmods.dev/skills/cloudai-x/opencode-workflow/parallel-execution"><img src="https://agentmods.dev/badge/skills/cloudai-x/opencode-workflow/parallel-execution/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.
<a href="https://agentmods.dev/skills/cloudai-x/opencode-workflow/parallel-execution"><img src="https://agentmods.dev/badge/skills/cloudai-x/opencode-workflow/parallel-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00037 | $0.02047 |
| Opus 5.5 | $0.00015 | $0.00819 |
| Sonnet 5.5 | $0.00007 | $0.00409 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
parallel-execution 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Execution
CRITICAL: This skill teaches how to execute multiple tasks simultaneously for maximum efficiency.
The Fundamental Rule
ALL Task calls MUST be in a SINGLE assistant message for true parallelism.
If Task calls are in separate messages, they run SEQUENTIALLY, not in parallel.
Why Parallel Execution Matters
Sequential (SLOW - AVOID)
Message 1: Start Task A
↓ wait for completion
Message 2: Start Task B
↓ wait for completion
Message 3: Start Task C
↓ wait for completion
Total time = A + B + C = 90 seconds (if each takes 30s)
Parallel (FAST - USE THIS)
Message 1: Start Task A ─┐
Start Task B ─┼─ All run simultaneously
Start Task C ─┘
Total time ≈ max(A, B, C) = 30 seconds
Speedup: 3x faster with 3 parallel tasks
How to Execute in Parallel
Step 1: Identify Independent Tasks
Tasks are independent when:
- They don't depend on each other's output
- They don't modify the same files
- They can run in any order
Step 2: Launch ALL Tasks in ONE Message
<!-- CORRECT: All tasks in single message = PARALLEL -->
<task>
<description>Analyze authentication module</description>
<prompt>Review src/auth for security patterns...</prompt>
</task>
<task>
<description>Analyze API layer</description>
<prompt>Review src/api for REST best practices...</prompt>
</task>
<task>
<description>Analyze database layer</description>
<prompt>Review src/db for query optimization...</prompt>
</task>
Step 3: Collect and Synthesize Results
After all tasks complete, combine their findings into a unified response.
Parallelization Patterns
Pattern 1: Task-Based Parallelization
When you have N independent tasks, spawn N subagents:
Implementation Plan:
1. Implement auth module
2. Create API endpoints
3. Add database schema
4. Write unit tests
5. Update documentation
Launch 5 parallel subagents:
├─ Subagent 1: Implement auth module
├─ Subagent 2: Create API endpoints
├─ Subagent 3: Add database schema
├─ Subagent 4: Write unit tests
└─ Subagent 5: Update documentation
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.
- 1mo ago First seen · 365 lines · 37 tokens per session scan A 464556bf2730
parallel-execution is a skill published in the GitHub repository CloudAI-X/opencode-workflow (275 stars, last pushed 9mo ago), licensed MIT. It adds 37 tokens to every session and 2,047 once invoked, about $0.0001 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…