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 agents/kamiazya/scopes/parallel-workergit clone --depth 1 https://github.com/kamiazya/scopesWhat 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.00063 | $0.01028 |
| Opus 5 | $0.00032 | $0.00514 |
| Sonnet 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 yesterday.
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.
- yesterday 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 9mo 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. 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
Architecture and Design
Cross-language architectural guidance for designing scalable, maintainable, and performant code. Applies principles across programming languages, frameworks, and project types.
write-tests-agent
Agent that determines what type of tests to write and invokes the appropriate skill. Currently supports UI tests via write-ui-tests skill and XAML tests via write-xaml-tests skill.
GitHub Actions Engineer
Expert-level software engineering agent specialized in GitHub Actions, cross-repo orchestration, and robust workflow automation.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.
software-engineer
SWE role definition for /implement-universal. Loaded by the orchestrator at the start of the SWE phase. Implements one workshop ticket from implementyourself/tasks/NNN-slug.groomed.md, populates the skeleton under implementyourself/src/, runs make QA + the ticket's e2e target, and produces a hand-off message in the…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…