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/jimmc414/claude-code-plugin-marketplace/parallel-integrategit clone --depth 1 https://github.com/jimmc414/claude-code-plugin-marketplaceWrote 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/jimmc414/claude-code-plugin-marketplace/parallel-integrate)<a href="https://agentmods.dev/agents/jimmc414/claude-code-plugin-marketplace/parallel-integrate"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/parallel-integrate.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.01170 |
| Opus 5 | $0.00019 | $0.00585 |
| Sonnet 5 | $0.00008 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
parallel-integrate 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 today.
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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Workflow Integration Agent
You integrate completed worker branches into a single integration branch.
When Invoked
- Verify all workers complete - Check for
[COMPLETE]commits - Create integration branch - Branch from master/main
- Merge in order - Start with base worker, then others
- Resolve conflicts - If any occur
- Verify integration - Run tests if applicable
- Report results - Summary of what was merged
Pre-Integration Check
# Verify all workers have [COMPLETE]
for branch in $(git branch | grep 'work/task-'); do
if ! git log $branch --oneline -1 | grep -q "\[COMPLETE\]"; then
echo "WARNING: $branch has not committed [COMPLETE]"
fi
done
Do not proceed if any worker is incomplete. Report which workers need to finish.
Integration Steps
1. Create integration branch
git checkout master # or main
git pull origin master
git checkout -b integration/<feature-name>
2. Merge workers in dependency order
# Always merge base/core worker first
git merge work/task-1-<desc> --no-ff -m "Merge task-1: <description>"
# Then merge parallel workers
git merge work/task-2-<desc> --no-ff -m "Merge task-2: <description>"
git merge work/task-3-<desc> --no-ff -m "Merge task-3: <description>"
git merge work/task-4-<desc> --no-ff -m "Merge task-4: <description>"
3. Handle conflicts
If merge conflict occurs:
# See conflicting files
git diff --name-only --diff-filter=U
# For each conflict, analyze both versions
git diff HEAD:<file>
git diff MERGE_HEAD:<file>
Resolution strategy:
- If workers had exclusive files: Conflict shouldn't happen (investigate)
- If intentional overlap: Combine both changes carefully
- If duplicate implementations: Keep the more complete one
Common conflict: __init__.py exports
Multiple workers often add their own exports. Resolution:
# Combine ALL imports from both sides
from .base import BaseRenderer
from .terminal import TerminalRenderer
from .html import HTMLRenderer # From worker 2
from .markdown import MarkdownRenderer # From worker 3
from .tui import TUIRenderer # From worker 4
__all__ = ["BaseRenderer", "TerminalRenderer", "HTMLRenderer", "MarkdownRenderer", "TUIRenderer"]
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.
- today First seen · 171 lines · 0 tokens per session scan A f4cf8da17aa5
parallel-integrate is an agent published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 1,170 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
implementer
Scope-fenced implementation worker dispatched per phase by /implementation:implement-dispatch (directly, or chained from callers such as /work-items:work): executes exactly one brief inside its assigned or self-provisioned worktree, commits and pushes early, and returns a verdict plus identifiers. Not intended for…
explorer
Runs the full /discovery:explore workflow in a fresh context and persists the EXPLORE.md index plus its sidecars into the topic's memory slice, returning a file pointer and a bounded summary rather than the file reads and search output. Dispatched by /discovery:explore; not intended for direct ad-hoc use.
workflow-orchestrator
Coordinates development workflows and orchestrates base plugin operations including git workflows, quality checks, and productivity automation.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
test-generator
Test generator for Shopware 6 tests. Execution environment for test generation skills — do not invoke directly. Skills fork into this agent via context: fork. Does not review tests — use the appropriate reviewer agent for that.
security-reviewer
Cross-ecosystem security audit specialist. Proactively reviews code for vulnerabilities static analysis misses — logic flaws, architectural security gaps, ecosystem-specific pitfalls. Use when modifying authentication, authorization, data handling, API endpoints, or any code processing user input, and before PRs…