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 LucasSantana-Dev/sharekit --skill parallel-work-coordinatorgit clone --depth 1 https://github.com/LucasSantana-Dev/sharekitWrote 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/lucassantana-dev/sharekit/parallel-work-coordinator)<a href="https://agentmods.dev/skills/lucassantana-dev/sharekit/parallel-work-coordinator"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/parallel-work-coordinator/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/lucassantana-dev/sharekit/parallel-work-coordinator"><img src="https://agentmods.dev/badge/skills/lucassantana-dev/sharekit/parallel-work-coordinator.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.00089 | $0.01876 |
| Opus 5.5 | $0.00036 | $0.00750 |
| Sonnet 5.5 | $0.00018 | $0.00375 |
| Haiku 4.5 | $0.00009 | $0.00188 |
Grade A, and why
parallel-work-coordinator 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Work Coordinator
Dispatch independent work units in parallel with sensible defaults, collect results, and reconcile findings without Workflow overhead.
When to use
- Multi-repo sweeps: "Audit these 4 repos for security issues"
- Multi-file operations: "Translate these 3 document groups to PT-BR"
- Parallel investigations: "Check these 5 error logs for the same root cause"
- Fan-out analysis: "Review each of these 4 approach proposals for feasibility"
- When you detect sequential-by-default: User is about to run N independent tasks one-by-one; suggest parallelism
Boundary: If work has cross-unit dependencies (task B needs output from task A) or requires loops/conditionals, use /loop or the Workflow tool instead. This skill is for the happy path — fully independent units.
Why this matters
CLAUDE.md hard rule #2: "Parallel execution is mandatory for ≥2 independent tasks." But setting up Workflow requires a YAML script and cloud billing. For 3–5 independent tasks with no interdependencies, this skill provides the structure without the overhead — and enforces the mandatory parallelism.
Workflow
Phase 1 — Scan & Decompose
Read the user's request or the active plan. Extract independent work units:
- Example 1: "Audit repos A, B, C for security" → 3 units (one per repo, independent)
- Example 2: "Translate files X, Y, Z to PT-BR" → 3 units (one per file group, independent)
- Example 3: "Check logs 1–5 for root cause" → 1 unit (they share context; run as one sweep, not 5 independent sweeps)
Key question: Does unit B need the output of unit A? If yes → not independent. Flag it, note the dependency, and suggest sequential execution instead.
Output: N independent units identified (or "these are not truly independent — recommend sequential execution instead").
Done when: all N units decomposed and dependencies mapped.
Phase 2 — Plan Dispatch
For each unit:
- Assign a label (short, descriptive:
repo-a-security,pt-br-files-1-50, etc.) - Assign a worktree path (if the unit touches a git repo):
- If 2+ units touch the same repo → each unit gets its own worktree:
${DEV_ROOT}/.worktrees/<label>-<n>/ - If each unit touches a different repo → no worktree needed (work in place)
- If 2+ units touch the same repo → each unit gets its own worktree:
- Draft an agent prompt (what the agent should do for this unit; include the scope and success criteria)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 140 lines · 89 tokens per session scan A 68918d4bc0e4
parallel-work-coordinator is a skill published in the GitHub repository LucasSantana-Dev/sharekit (1 stars, last pushed 3d ago), licensed MIT. It adds 89 tokens to every session and 1,876 once invoked, about $0.0004 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-03.
Other skills, from other repositories
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
ulw-execute
Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.