Borrowing it
Nothing to install: this file belongs to ArieGoldkin/ai-agent-hub. 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/ArieGoldkin/ai-agent-hub/main/.squad/commands/allocate-tasks-parallel.mdgit clone --depth 1 https://github.com/ArieGoldkin/ai-agent-hubWrote 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/ariegoldkin/ai-agent-hub/allocate-tasks-parallel)<a href="https://agentmods.dev/commands/ariegoldkin/ai-agent-hub/allocate-tasks-parallel"><img src="https://agentmods.dev/badge/commands/ariegoldkin/ai-agent-hub/allocate-tasks-parallel/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/ariegoldkin/ai-agent-hub/allocate-tasks-parallel"><img src="https://agentmods.dev/badge/commands/ariegoldkin/ai-agent-hub/allocate-tasks-parallel.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.02909 |
| Opus 5 | $0.00000 | $0.01455 |
| Sonnet 5 | $0.00000 | $0.00582 |
| Haiku 4.5 | $0.00000 | $0.00291 |
Grade A, and why
allocate-tasks-parallel 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.
How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Allocate Tasks for Parallel Execution
INTERACTION MODE: REQUIRED
This command requires user interaction. You MUST wait for user input before proceeding.
You are responsible for analyzing feature requirements and distributing work across multiple agents to enable parallel execution.
STEP 1: Gather Requirements
FIRST ACTION: Check if the user provided requirements with this command.
Automatic PRD Detection
First, search for existing PRD files using the bash commands in the Execution Instructions section.
IMPORTANT: When searching for PRDs:
- EXCLUDE any files in
.squad/examples/directory - EXCLUDE any files in
.claude/directory - EXCLUDE any files in
templates/ortest/directories - These are example/template files, NOT actual project requirements
If the search returns "NO_PRD_FOUND - User input required" OR if NO requirements were provided:
-
STOP and ask the user directly: "📋 What would you like to build?
Please describe your requirements and I'll allocate tasks across multiple agents for parallel execution."
-
WAIT for the user to respond with their requirements
-
DO NOT proceed until the user provides their input
-
DO NOT create any files or generate any output until requirements are received
-
DO NOT use example PRDs from
.squad/examples/as actual requirements
If requirements WERE provided with the command OR a valid PRD was found:
- Proceed directly to Step 2
STEP 2: Process Requirements
Only after receiving requirements from the user, proceed with allocation:
DEFAULT TECHNOLOGY STACK
CRITICAL: Unless explicitly specified otherwise, use these defaults:
Backend
- Language: TypeScript (Node.js 18+)
- Framework: Express.js or Fastify
- Files: .ts extension only
- Package Manager: npm
- Config: tsconfig.json with strict mode
Frontend
- Language: TypeScript + React 18+
- Framework: Vite for build tooling
- Files: .tsx for components, .ts for utilities
- Styling: Tailwind CSS or CSS Modules
- State: Context API or Zustand
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.
- 9d ago First seen · 376 lines · 0 tokens per session scan A 7114b72478cf
allocate-tasks-parallel is a command published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,909 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.