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.
git 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/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/jimmc414/claude-code-plugin-marketplace/parallel-integrate"><img src="https://agentmods.dev/badge/agents/jimmc414/claude-code-plugin-marketplace/parallel-integrate.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.00000 | $0.01170 |
| Opus 5.5 | $0.00000 | $0.00468 |
| Sonnet 5.5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $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 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 — 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.
- 1mo ago 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 costs nothing until one of its globs matches a file; then it loads 1,170 tokens. 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 unless the brief reserves commit authority to the…
scoped-implementer
Scope-fenced implementation worker for a phase the plan's routing table marks sonnet (closed scope fence, binary acceptance criteria, no open design decision, no cross-module contract change, no security-surface work), dispatched by /implementation:implement-dispatch with an explicit per-invocation model: executes…
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
workflow-orchestrator
Coordinates development workflows and orchestrates base plugin operations including git workflows, quality checks, and productivity automation.
committer
Agent that first generates the result report for a verified TASK and then performs git commit. Automatically invoked by the scheduler. Result files are created in the corresponding WORK directory.
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.