Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jdrhyne/agent-skillsnpx agentmods add skills/jdrhyne/agent-skills/parallel-taskWrote 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/jdrhyne/agent-skills/parallel-task)<a href="https://agentmods.dev/skills/jdrhyne/agent-skills/parallel-task"><img src="https://agentmods.dev/badge/skills/jdrhyne/agent-skills/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/skills/jdrhyne/agent-skills/parallel-task"><img src="https://agentmods.dev/badge/skills/jdrhyne/agent-skills/parallel-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00027 | $0.00982 |
| Opus 5.5 | $0.00011 | $0.00393 |
| Sonnet 5.5 | $0.00005 | $0.00196 |
| Haiku 4.5 | $0.00003 | $0.00098 |
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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Task Runner
Use Orchestration Mode. Parse plan files and delegate tasks to parallel subagents.
Safety Boundaries
- Do not launch subagents for tasks that share write scope until the dependency is resolved.
- Do not continue past blockers silently; surface the blocked task and stop that branch of work.
- Do not mark tasks complete until validation from the plan has actually been checked.
- Do not run this skill unless the user explicitly invoked
/parallel-taskor clearly asked for parallel agent work.
Process
Step 1: Parse Request
Extract from user request:
- Plan file: The markdown plan to read
- Sprint/Phase (optional): Which section to run
If sprint not provided, ask user which to run.
Step 2: Read & Parse Plan
- Find sprint/phase section (e.g.,
## Sprint 1:) - Extract task subsections (e.g.,
### Task 1.1:) - For each task, extract:
- Task ID and name
- Full content (description, location, acceptance criteria, validation)
- Build task list
Step 3: Launch Subagents
For each task, launch subagent with:
- description: "Implement task [ID]: [name]"
- prompt: Use template below
If there are multiple unblocked tasks, launch multiple subagents in parallel.
Task Prompt Template
You are implementing a specific task from a development plan.
## Context
- Plan: [filename] - [sprint/phase]
- Goals: [relevant overview from plan]
- Dependencies: [prerequisites for this task]
- Related tasks: [tasks in same sprint]
- Constraints: [risks from plan]
## Your Task
**Task [ID]: [Name]**
Location: [File paths]
Description: [Full description]
Acceptance Criteria:
[List from plan]
Validation:
[Tests or verification from plan]
## Instructions
1. Examine and explore the plan, all relevant files & dependencies. Ensure ambiguities are cleared up.
2. Implement changes for all acceptance criteria
3. Keep work **atomic and committable**
4. For each file: read first, edit carefully, preserve formatting
5. Run validation if feasible
6. Return summary of:
- Files modified/created
- Changes made
- How criteria are satisfied
- Validation performed or deferred
## Important
- Be careful with paths
- Stop and describe blockers if encountered
- Focus on this specific task
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 · 159 lines · 27 tokens per session scan A e6a3c38a4f28
parallel-task is a skill published in the GitHub repository jdrhyne/agent-skills (240 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 982 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
pillow
Manipulate images locally using Python and PIL/Pillow. Use when the user asks to resize, crop, rotate, flip, filter, enhance, combine, overlay, watermark, add text to, convert, compress, create, or edit images locally. Also use for thumbnails, borders, color adjustments, transparency, animated GIFs, or extracting…
skill-creator
Create or update OpenBotX skills. Use when users want to create a new skill, modify an existing one, or need guidance on skill structure, frontmatter, bundled resources, or best practices. Also use when the user says "turn this into a skill" or wants to capture a workflow as a reusable skill.
http-client
Make HTTP requests (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS) to APIs and web services. Use when the user needs to call a REST API, fetch data from an endpoint, send form data, upload files, download files, or test HTTP services.
browser
Automate browser interactions for web scraping, testing, and navigation. Use when the user needs to visit a webpage, interact with UI elements, take screenshots, or extract content from rendered pages.
Post tweets on Twitter/X. Use when the user wants to tweet, post on X, create threads, or share content on Twitter. Requires the "twitter" auth profile configured in httpclient.
cron
Schedule reminders, recurring tasks, and one-time events. Use when the user asks to be reminded of something, schedule a periodic check, set an alarm, or automate a task at a specific time or interval.