Borrowing it
Nothing to install: this file belongs to yasuflatland-lf/liferay-dummy-factory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yasuflatland-lf/liferay-dummy-factory/master/.claude/skills/parallel-orchestration/SKILL.mdgit clone --depth 1 https://github.com/yasuflatland-lf/liferay-dummy-factoryWrote 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/yasuflatland-lf/liferay-dummy-factory/parallel-orchestration)<a href="https://agentmods.dev/skills/yasuflatland-lf/liferay-dummy-factory/parallel-orchestration"><img src="https://agentmods.dev/badge/skills/yasuflatland-lf/liferay-dummy-factory/parallel-orchestration/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/yasuflatland-lf/liferay-dummy-factory/parallel-orchestration"><img src="https://agentmods.dev/badge/skills/yasuflatland-lf/liferay-dummy-factory/parallel-orchestration.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.00043 | $0.01165 |
| Opus 5.5 | $0.00017 | $0.00466 |
| Sonnet 5.5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
parallel-orchestration 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 20d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Orchestration Workflow
Template for running multi-agent work where the main Claude Code session coordinates and sub-agents execute.
Roles
- Main agent — orchestration only. MUST NOT read, edit, or run code directly. Its job is to decompose the task, dispatch sub-agents, aggregate their reports, and decide the next phase.
- Sub-agents — execute one scoped unit of work each. Run in parallel whenever their file clusters are independent.
- Commit agent — a dedicated, single, serial agent responsible for every git commit. No other agent commits.
Parallelism rules
- Dispatch sub-agents in parallel whenever their working sets do not overlap. Partition by file cluster, not by task phase.
- If two sub-agents would touch the same file, serialize them — never let two agents race the same path.
- The main agent waits for all parallel sub-agents in a wave to report before starting the next wave.
Commit rules
- Commits are serialized through the single commit agent. Sub-agents stage nothing and push nothing.
- Commit messages are one line. No
Co-Authored-Bytrailers, no body text, no emoji. - One logical change per commit. If a sub-agent produced two unrelated fixes, the commit agent splits them.
Context hygiene
- When a sub-agent's remaining context budget drops to 5% or below, run
/compactbefore continuing. Preserve: discovered solutions, final decisions, file paths that matter. Drop: debug transcripts, failed attempts, raw tool output. - The main agent's own context should stay lean — it holds plans and summaries, not source code.
Four-phase pattern
- Explore — one or more read-only sub-agents map the relevant code, answer "what exists, where, and how is it wired?". Output: a written summary with absolute file paths.
- Design — main agent (or a dedicated design sub-agent) turns the exploration into a plan: file clusters, sub-agent assignments, dependencies. Output: a task list with clear ownership boundaries.
- Implement — parallel sub-agents edit their clusters. Each reports completion with a diff summary.
- Review → Simplify → Verify — a review sub-agent reads the diffs, a simplify sub-agent removes dead code / redundancy, and a verify sub-agent runs the actual build/test commands. Only after verify is green does the commit agent run.
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.
- 20d ago First seen · 94 lines · 43 tokens per session scan A 9387f5fdc88f
parallel-orchestration is a skill published in the GitHub repository yasuflatland-lf/liferay-dummy-factory (50 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,165 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
misata
Generate relational test, demo or evaluation data from a declared schema with Misata, where every declaration (foreign keys, unique and CHECK rules, monthly revenue curves, rates, group shares, ledger identities) holds exactly or is refused before generation, then attest the files. Use when a task needs a seeded…
keynobi
Use for Android work that needs state kept between calls - Gradle builds with their errors and history, logcat streaming and filtering, crashes and deobfuscated stack traces, app exit reasons, launch times, debug sessions that record each install and what followed, and UI automation on the running app - through the…
use-siteation-debugbar
Inspect Magento requests through SiteationDebugBar's MCP server. Use when asked why a page is slow, what a request did, which queries or observers ran, or to explain an error on a Magento store running this module.
rr-debug-logic
Debug a logic bug (wrong output, wrong value, incorrect behavior) using rr. Sets breakpoints at the point where the bug is observable, then reverse-executes to find where the computation went wrong.
rr-debug-race
Debug a data race or concurrency bug using rr. Records the program, then uses deterministic replay with thread inspection and watchpoints to find the exact interleaving that caused the race.
rr-debug
Debug a crash or test failure using rr reverse debugging. Records a command, replays it, and works backwards from the failure to find the root cause.