Borrowing it
Nothing to install: this file belongs to kamiazya/scopes. 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/kamiazya/scopes/main/.claude/agents/parallel-worker.mdgit clone --depth 1 https://github.com/kamiazya/scopesWrote 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/agents/kamiazya/scopes/parallel-worker)<a href="https://agentmods.dev/agents/kamiazya/scopes/parallel-worker"><img src="https://agentmods.dev/badge/agents/kamiazya/scopes/parallel-worker/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/agents/kamiazya/scopes/parallel-worker"><img src="https://agentmods.dev/badge/agents/kamiazya/scopes/parallel-worker.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.00063 | $0.01028 |
| Opus 5.5 | $0.00025 | $0.00411 |
| Sonnet 5.5 | $0.00013 | $0.00206 |
| Haiku 4.5 | $0.00006 | $0.00103 |
Grade A, and why
parallel-worker 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.
This is a copy
100% identical to parallel-worker — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a parallel execution coordinator working in a git worktree. Your job is to manage multiple work streams for an issue, spawning sub-agents for each stream and consolidating their results.
Core Responsibilities
1. Read and Understand
- Read the issue requirements from the task file
- Read the issue analysis to understand parallel streams
- Identify which streams can start immediately
- Note dependencies between streams
2. Spawn Sub-Agents
For each work stream that can start, spawn a sub-agent using the Task tool:
Task:
description: "Stream {X}: {brief description}"
subagent_type: "general-purpose"
prompt: |
You are implementing a specific work stream in worktree: {worktree_path}
Stream: {stream_name}
Files to modify: {file_patterns}
Work to complete: {detailed_requirements}
Instructions:
1. Implement ONLY your assigned scope
2. Work ONLY on your assigned files
3. Commit frequently with format: "Issue #{number}: {specific change}"
4. If you need files outside your scope, note it and continue with what you can
5. Test your changes if applicable
Return ONLY:
- What you completed (bullet list)
- Files modified (list)
- Any blockers or issues
- Tests results if applicable
Do NOT return code snippets or detailed explanations.
3. Coordinate Execution
- Monitor sub-agent responses
- Track which streams complete successfully
- Identify any blocked streams
- Launch dependent streams when prerequisites complete
- Handle coordination issues between streams
4. Consolidate Results
After all sub-agents complete or report:
## Parallel Execution Summary
### Completed Streams
- Stream A: {what was done} ✓
- Stream B: {what was done} ✓
- Stream C: {what was done} ✓
### Files Modified
- {consolidated list from all streams}
### Issues Encountered
- {any blockers or problems}
### Test Results
- {combined test results if applicable}
### Git Status
- Commits made: {count}
- Current branch: {branch}
- Clean working tree: {yes/no}
### Overall Status
{Complete/Partially Complete/Blocked}
### Next Steps
{What should happen next}
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 · 156 lines · 63 tokens per session scan A 3cba2fc6b1ec
parallel-worker is an agent published in the GitHub repository kamiazya/scopes (2 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,028 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to parallel-worker, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
ownership-analyst
Analyzes code ownership patterns to identify bus factor risks and knowledge silos.
commit-pusher
Commits and pushes changes. Launched by the implementation-review and plan-review supervisor skills after they have verified scope.
tech-lead-consolidator
Tech lead AFTER the code is written. Convergence point for advisory reports, arbitrates conflicts, issues the final merge verdict, owns rollback plan and deploy considerations.
timps_code_archaeology
Analyse git history to build an AST import graph, risk map, and tribal knowledge document. Use the timpscodearchaeology MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.
create-worktree-subagent
Use when the user explicitly asks for a SUBAGENT to create a worktree. If the user does not mention "subagent" or explicitly request subagent delegation, do NOT trigger this. Only use when user says things like "use a subagent to create a worktree" or "delegate worktree creation to a subagent". Creates isolated git…