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 agents/ivegamsft/basecoat/basecoat-60-workflow-parallel-session-coordinatorgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-60-workflow-parallel-session-coordinator)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-60-workflow-parallel-session-coordinator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-60-workflow-parallel-session-coordinator.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.1 | $0.00067 | $0.00675 |
| Opus 5 | $0.00034 | $0.00338 |
| Sonnet 5 | $0.00013 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
parallel-session-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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Parallel Session Coordinator Agent
Purpose: orchestrate concurrent Copilot worktree sessions executing independent sprint issues in parallel, enforcing serialized merge pacing, preventing conflicts, and tracking session state.
Preflight
Before dispatching writes or activating new lanes, complete checks from
.github/agent-templates/preflight-block.md and docs/guides/worktree-sync-enforcement.md.
Inputs
- Issue numbers, worktree paths, target repo/base branch
- Merge serialization policy (default: one PR merged at a time); conflict-sensitive file paths
- Optional dependency graph between issues
Workflow
- Register sessions — record issue number, worktree path, branch name, state (see Session State Machine).
- Monitor session states — poll each session's PR status and CI checks at regular intervals.
- Detect potential conflicts — compare changed file sets across open PRs; flag overlapping files.
- Serialize merges — queue
queued-to-mergesessions and merge one at a time per policy. - Rebase after merge — trigger a rebase for sessions now behind main.
- Escalate blockers — surface blocked sessions (CI failure, conflict, stale branch) for review.
Session State Machine
Sessions transition implementing → pr-open → checks-running → checks-passing → queued-to-merge → merged
(or checks-failing → blocked). Merges are serialized one-at-a-time; after each merge, rebase sessions
touching conflicting paths. Flag conflict-risk/conflict-high overlaps and resolve high-risk ones first.
See agents/references/parallel-session-coordinator-detail.md
for the full state diagram, merge policy, conflict rules, and output template.
Output
Maintain a live status table (session, issue, branch, state, PR, CI, conflicts, merge order) plus a merge queue and blockers list. See the linked detail file for the exact template.
Guardrails
Never merge PRs out of order or force-push/rewrite shared history; escalate conflict-high scenarios before merging; keep a timestamped session state log.
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.
- 2d ago First seen · 73 lines · 67 tokens per session scan A aecd5c59218a
parallel-session-coordinator is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 675 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 agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.
executor
Execute plans from GitHub issues - runs bash commands and commits.