What is coordination-bus?

A coordination system for multiple coding agents or sessions sharing tasks. It records who owns each task and whether work is active, finished, or blocked.

Use it to claim tasks, send progress heartbeats, mark work complete or blocked, and check task ownership during shared work.

It prevents two agents from changing the same work and makes task ownership visible to everyone.

coordination-bus — Skill for Claude Code by oyi77/1ai-skills

Install

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.

Any agent

npx skills add oyi77/1ai-skills --skill coordination-bus

Clone the repo

git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 212 skills, 4 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/oyi77/1ai-skills/coordination-bus/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/coordination-bus)

Your own site

<a href="https://agentmods.dev/skills/oyi77/1ai-skills/coordination-bus"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/coordination-bus/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/oyi77/1ai-skills/coordination-bus"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/coordination-bus.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 867 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00056	$0.00867
Opus 5.5	$0.00022	$0.00347
Sonnet 5.5	$0.00011	$0.00173
Haiku 4.5	$0.00006	$0.00087

Measured 1mo ago against content hash be5c0c98978a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coordination-bus 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.

core/coordination-bus/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coordination Bus

When to Use

Trigger phrases:

"claim task", "coord status", "coordination status", "bus status"
"heartbeat task", "complete task", "block task"
Any multi-agent or multi-session work (RULES.md Rule 19)

Use cases:

Claiming ownership of shared work before starting
Signalling liveness while working
Completing or blocking with a reason
Checking who owns what before touching shared files

When NOT to use:

Single-agent single-session trivial work (no bus needed)
PaperClip issues (separate tracker — bus is for runtime ownership, not backlog)

Overview

The coordination bus (1ai-hub /coordination) records WHO owns WHAT task, what it depends on, and whether product-gate docs exist. A second claim on an owned task is rejected — the rejection is the conflict signal, not a bug.

Protocol

Claim before work: claim <task-id> as <your-agent-id> — via chat (CoordinationExecutor) or REST POST /coordination/tasks/{id}/claim with {"owner_agent": "..."}.
Heartbeat while working: heartbeat <task-id> as <owner> or POST .../heartbeat. First heartbeat moves claimed → in_progress. Stale heartbeat (>15 min) flags the task stuck in daemon supervision.
Finish: complete <task-id> as <owner> or POST .../complete. Blocked: block <task-id> as <owner>: <reason> or POST .../block with {"reason": "..."}.
Dependencies: a task with depends_on cannot be claimed until the dependency is done. The bus rejects with blocked: dependency <id> is <status>.
Product gate: user-facing tasks carry gate_required. Record docs via POST .../gate-docs with {"docs": "path/to/brainstorm.md,..."} before active work. Daemon flags gate violations every 60s.

Status

Chat: coord status [repo] — active tasks, stuck list, gate violations.
REST: GET /coordination/active?repo=, GET /coordination/stuck, GET /coordination/gate-violations.

Anti-Rationalization Table

Rationalization	Reality
"I'll just tell the other agent directly"	Private agreement is invisible to the daemon. Claim on the bus or the work doesn't exist.
"The claim rejection is a bug"	The rejection IS the conflict signal. Talk to the owner, don't retry.
"Gate docs later"	Active work without gate docs is flagged every 60s. Record docs first.
"Small task, skip the bus"	If two agents can touch it, it's not small. Claim it.

Read the full file on GitHub · 76 lines

Changes

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 · 76 lines · 56 tokens per session scan A be5c0c98978a

Subscribe to this mod's changes

coordination-bus is a skill published in the GitHub repository oyi77/1ai-skills (16 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 867 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-09-17.

Multi-Agent Orchestration Project management agent ai-agent ai-automation ai-skills automation claude coordination core task-bus teamwork

cross-agent-handoff

Transfer context between AI agent sessions with structured handoff protocols, state serialization, and decision log preservation. Covers multi-agent coordination, context compression, and continuity patterns. Triggers on agent handoff, session transfer, or multi-agent continuity requests.

organvm-iv-taxis/a-i--skills · 53 tokens

dispatch

Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…

jeremylongshore/tons-of-skills-marketplace · 81 tokens

coordination-bus