Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/parallel-task.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/commands/regardv/legendaryteam_for_claude/parallel-task)<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/parallel-task"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/parallel-task/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/commands/regardv/legendaryteam_for_claude/parallel-task"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/parallel-task.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.00000 | $0.01795 |
| Opus 5.5 | $0.00000 | $0.00718 |
| Sonnet 5.5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00179 |
Grade A, and why
parallel-task 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/parallel-task - Parallel Plan Execution
Purpose
Executes a structured plan in parallel waves, spawning appropriate agents for each task based on dependencies and confidence routing.
Usage
/parallel-task [plan-file]
/parallel-task thoughts/shared/plans/plan-auth-001.md
/parallel-task plan-auth-001 # Shorthand (searches plans folder)
/parallel-task --resume # Resume last incomplete execution
Options
| Option | Description |
|---|---|
| --dry-run | Preview execution without running |
| --wave N | Start from specific wave |
| --resume | Resume interrupted execution |
| --sequential | Force sequential execution (no parallelism) |
| --verbose | Show detailed progress |
Execution Flow
1. Plan Loading
Loading plan: thoughts/shared/plans/plan-auth-001.md
Plan Summary:
├─ Goal: Build user authentication system
├─ Tasks: 8
├─ Waves: 4
├─ Auto-proceed: 7
├─ Queued: 1 (OAuth - needs review)
└─ Blocked: 0
Ready to execute. Proceed? [Y/n]
2. Wave Execution
═══════════════════════════════════════════════════════════
WAVE 1 EXECUTION - Foundation
═══════════════════════════════════════════════════════════
Spawning 1 team:
🚀 Team 1: @DatabaseAgent → T1 (User schema)
Progress:
├─ T1: ████████░░ 80% Creating migrations...
Wave 1 Complete ✓
Duration: 5 minutes
Results: 1/1 successful
═══════════════════════════════════════════════════════════
WAVE 2 EXECUTION - Core Services
═══════════════════════════════════════════════════════════
Spawning 2 teams in parallel:
🚀 Team 2: @SecurityAgent → T2 (Auth service)
🚀 Team 3: @SecurityAgent → T4 (Password hashing)
Progress:
├─ T2: ██████████ 100% ✓ Complete
├─ T4: ████████░░ 80% Testing...
Wave 2 Complete ✓
Duration: 12 minutes
Results: 2/2 successful
3. Confidence-Based Routing
During execution, tasks are routed based on confidence:
Wave 3 Execution:
AUTO-PROCEED (confidence ≥70%):
├─ T3 (85%): @APIAgent → Spawning immediately
├─ T6 (80%): @UIAgent → Spawning immediately
QUEUED (confidence 40-69%):
├─ T5 (55%): OAuth Integration
│ └─ Added to review queue
│ └─ Continuing with other tasks (non-blocking)
│ └─ Run /approve-task T5 when ready
High-confidence work continues while T5 awaits review.
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 · 270 lines · 0 tokens per session scan A 2ad5fdb1b836
parallel-task is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,795 tokens. 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 commands, from other repositories
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
close-track
Close a completed track — run quality gate, update conductor state, commit, and optionally handle the git branch.
mpm-init
Initialize or update project for Claude Code and MPM.
ocean-stop
Gracefully stop the boil-ocean run and its scheduler.
init-rules
Auto-generate .claude/rules/ — path-scoped coding conventions from project analysis. Re-run after codebase changes to update rules while preserving manually added conventions.