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 agentmods add skills/versoxbt/claude-initial-setup/parallel-task-executionnpx skills add VersoXBT/claude-initial-setup --skill parallel-task-executiongit clone --depth 1 https://github.com/VersoXBT/claude-initial-setupWhat 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 | $0.00047 | $0.01354 |
| Opus 5 | $0.00023 | $0.00677 |
| Sonnet 5 | $0.00009 | $0.00271 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
parallel-task-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 2d 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Task Execution
Claude Code can execute multiple independent tool calls in a single response. This dramatically reduces wall-clock time for tasks that do not depend on each other.
When to Use
- Multiple files need to be read, searched, or analyzed independently
- User wants to speed up a multi-step workflow
- Several subagents can investigate different aspects simultaneously
- Independent operations (read + grep + glob) can run concurrently
- User asks about fan-out/fan-in or parallel execution
Core Patterns
Identifying Independent Operations
Two operations are independent when neither needs the other's result. Test by asking: "Can I start operation B without knowing the result of operation A?"
# INDEPENDENT (run in parallel):
- Read file A and Read file B
- Grep for pattern X and Grep for pattern Y
- Analyze auth module and Analyze database module
# DEPENDENT (run sequentially):
- Find the config file, THEN read it
- Read the test file, THEN modify it based on contents
- Get the function signature, THEN find all call sites
Parallel Tool Calls
Make multiple tool calls in a single response block:
# Single response with 3 parallel calls:
Call 1 - Read:
file_path: "src/auth/middleware.ts"
Call 2 - Read:
file_path: "src/auth/tokens.ts"
Call 3 - Read:
file_path: "src/auth/permissions.ts"
All three files are read concurrently. Results arrive together for synthesis.
Fan-Out with Subagents
Launch multiple Agent tool calls for independent investigations:
# Fan-out: 3 parallel subagents
Agent 1:
prompt: "Analyze all React components in src/components/
for accessibility issues (missing aria labels,
no keyboard handlers). Report findings as a list."
Agent 2:
prompt: "Check all API routes in src/api/ for proper
error handling. Report which routes lack try/catch
or return generic error messages."
Agent 3:
prompt: "Review all database queries in src/db/
for N+1 query problems. Report file paths and
the specific query patterns."
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.
- 2d ago First seen · 185 lines · 47 tokens per session scan A 0258e8d246bf
parallel-task-execution is a skill published in the GitHub repository VersoXBT/claude-initial-setup (4 stars, last pushed 3mo ago), licensed MIT. It adds 47 tokens to every session and 1,354 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.