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 skills/vmobifystudio/app-dev-team/parallel-orchestratornpx skills add vmobifystudio/app-dev-team --skill parallel-orchestratorgit clone --depth 1 https://github.com/vmobifystudio/app-dev-teamWrote 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/vmobifystudio/app-dev-team/parallel-orchestrator)<a href="https://agentmods.dev/skills/vmobifystudio/app-dev-team/parallel-orchestrator"><img src="https://agentmods.dev/badge/skills/vmobifystudio/app-dev-team/parallel-orchestrator.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.00059 | $0.03941 |
| Opus 5 | $0.00030 | $0.01971 |
| Sonnet 5 | $0.00012 | $0.00788 |
| Haiku 4.5 | $0.00006 | $0.00394 |
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 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel orchestrator
You launch IC agents concurrently. This skill exists because parallel agent launches need rules — without them, agents stomp each other.
When to use
Called from /app-build or by the tech-manager once docs/31-board.md has tickets in todo ready to start.
Procedure
- Doctor gate. Run the
board-doctorskill first. If it exits non-zero, spawn nobody — a parallel launch against an incoherent board multiplies the damage across every track at once.
0a. Budget gate. The loop has no economic brake other than this one:
node "${CLAUDE_PLUGIN_ROOT}/scripts/round-journal.mjs" check
Exit 1 means a ceiling is reached: stop the loop, print the line verbatim, and report what
is unfinished. Do not start a round you cannot finish. Ceilings come from --max-rounds /
--max-spawns / --max-retries / --max-spend-usd, or APP_TEAM_MAX_* in the environment.
Raising one is a decision the user makes, not one you make to keep going.
-
Read the board. Find tickets where
Status = todoand allDepends onIDs are merged (qaordone) — a dependency is satisfied once its code is on the integration branch, not once QA has signed it off. Requiringdonestalls every dependent behind a QA pass.Read it from the log rather than the table where one exists —
node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" show --jsongives youstatusanddependsOnper ticket already derived.Note what this readiness rule cannot express: a ticket behind a
blockeddependency is not ready and never will be, but it is also never reported. That is the doctor'sstrandedcheck, and it is why step 0 exists.
1a. Claim before you spawn. One append per ticket, and it is also the readiness check you cannot forget to run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/board.mjs" move APP-001 claimed --by ios-developer
claimed is refused on a ticket whose dependency has never merged. That refusal is the
answer, not an obstacle: spawn nobody for that ticket and say why in the standup. Claiming before
the spawn also means the board says who is working on what while they work — the window in
which two orchestrators could both hand out the same ticket closes here.
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 · 269 lines · 59 tokens per session scan A d61797b2f476
parallel-orchestrator is a skill published in the GitHub repository vmobifystudio/app-dev-team (4 stars, last pushed 24d ago), licensed MIT. It adds 59 tokens to every session and 3,941 once invoked, about $0.0003 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-03.
Other skills, from other repositories
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".
good-first-issue-batch
File a batch of contributor-ready GitHub issues from the seeds backlog, re-verifying every candidate against HEAD first so no dead issue reaches a contributor. Activate for prompts like "file some good first issues", "open a batch of GFIs", "publish backlog issues to GitHub", "find contributor-ready work", or after an…
warren-dogfood-pipeline
Full prioritize → dispatch → shepherd → track pipeline against the live warren instance. Audits the seeds backlog around a focus theme, dispatches the surviving issues to warren agents one at a time, babysits the resulting PRs to merge (update-branch, conflict-repair runs, auto-merge), and closes the loop in the…
run
Conduct a task end to end, from a one-line fix to a multi-day programme - a short interview, then autonomous execution to the finish. Classifies the task S/M/L/XL, configures itself to the repo, routes each role to a cost tier, drives the agent team from the kanban board, and stops only at genuine decisions. Use for…
status
Where is the work right now. Regenerates the projections and the kanban board from the journal and answers with the progress line, the agents still running, the open gates and the resume steps. Read-only. Use for /tyran:status or when asked what is going on.
heartbeat
This skill should be used when the user asks to "run a heartbeat", "run the agent loop", "process GitHub issues", "check for work", or runs the /heartbeat command. Executes the WoterClip heartbeat — picks up GitHub issues, resolves personas, does work, and reports back.