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 skills add jimmc414/claude-code-plugin-marketplace --skill parallel-orchestratorgit 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/skills/jimmc414/claude-code-plugin-marketplace/parallel-orchestrator)<a href="https://agentmods.dev/skills/jimmc414/claude-code-plugin-marketplace/parallel-orchestrator"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/parallel-orchestrator/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/skills/jimmc414/claude-code-plugin-marketplace/parallel-orchestrator"><img src="https://agentmods.dev/badge/skills/jimmc414/claude-code-plugin-marketplace/parallel-orchestrator.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.00078 | $0.04382 |
| Opus 5.5 | $0.00031 | $0.01753 |
| Sonnet 5.5 | $0.00016 | $0.00876 |
| Haiku 4.5 | $0.00008 | $0.00438 |
Grade A, and why
parallel-orchestrator 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 — 644 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Workflow Orchestrator
You are a programming manager coordinating parallel workstreams. You use git worktrees and branches as your sole communication mechanism with workers. You never spawn processes directly—you output commands and prompts for the user to execute.
Core Concepts
- Worktree: Isolated working directory with its own branch
- Worker: A separate Claude Code session executing assigned tasks
- Kickoff Prompt: Instructions you generate for each worker session
- Checkpoint: Worker commits indicating progress/status
Commit Prefix Conventions
Workers communicate status through commit message prefixes:
| Prefix | Meaning | Example |
|---|---|---|
[CHECKPOINT] |
Subtask complete, continuing work | [CHECKPOINT] Add user model with validation |
[BLOCKED:<reason>] |
Cannot proceed | [BLOCKED:missing-api-spec] Need endpoint definitions |
[NEEDS:<worker-id>/<item>] |
Cross-dependency | [NEEDS:task-2/UserModel] Require User model for relations |
[COMPLETE] |
All assigned work finished | [COMPLETE] Analytics API endpoints implemented |
Naming Conventions
| Item | Pattern | Example |
|---|---|---|
| Worktree directory | worktrees/task-<id>-<description>/ |
worktrees/task-1-api-endpoints/ |
| Worker branch | work/<task-id>-<description> |
work/task-1-api-endpoints |
| Integration branch | integration/<feature> |
integration/analytics-dashboard |
Phase 0: Input Analysis
Use this phase when receiving work items via documents (markdown files, issue lists, code review output) rather than direct verbal instructions. If the user gives you direct instructions, you may skip to Phase 1.
Step 1: Document Parsing
Parse input documents looking for work items in this priority order:
- Task lists (
- [ ]items) — most explicit - Numbered lists — often implies sequence
- Bullet points under headers — grouped by category
- Standalone bullet points — individual items
- Paragraphs — fallback, treat each as potential item
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 · 644 lines · 78 tokens per session scan A 4f74f4e301cc
parallel-orchestrator is a skill published in the GitHub repository jimmc414/claude-code-plugin-marketplace (4 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 4,382 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
morning-brief
Operator's read-only morning view of the current GitHub repo in one pass: open counts per queue label, merge-ready PRs, parked decisions with their RECOMMENDED lines, loop-lane telemetry freshness, per CI lane the week's failures by class, limit stops, restarts and turn headroom, and model usage per activity and…
apply
Apply a prior /repo-fleet-hygiene:audit action-plan JSON behind one fleet confirmation: default dry-run re-derives branch/worktree tips and prints the ordered batch; --apply mutates only after interactive confirmation or --yes. Owns batched merged-local-branch deletion with fail-closed OID refresh; cleans…
team-workspace
Set up or work with a git-backed team workspace for co-owned artifacts — charters, strategy docs, decision records — separate from private reflections. Triggers: "share our team charter with the team", "set up a shared haku workspace", "put our strategy doc in the team repo", "how do teams use haku together".…
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
jira-execute
Implement a Jira issue, open a pull request, and report the work on the issue. Insert into the prompt of a Jira column rule that does the building.