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/yezannnnn/agentgroup/parallel-workergit clone --depth 1 https://github.com/yezannnnn/agentGroupWhat 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- parallel-worker — 100% identical, 0 lines differ
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.
- 2d ago First seen · 156 lines · 63 tokens per session scan A 3cba2fc6b1ec
parallel-worker is an agent published in the GitHub repository yezannnnn/agentGroup (149 stars, last pushed 3mo ago), licensed MIT. 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.