agentsclimarketplace

Agent bus

Skill adjcjh777/agent-bus-skills/skills/agent-bus

Codex Agent Bus skill family for local multi-agent coordination

Install
npx -y skills add adjcjh777/agent-bus-skills --skill agent-bus

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Route Agent Bus multi-agent coordination workflows across registration, delegation, teams, and diagnostics. Use when the user asks generally about Agent Bus, multi-agent coordination, cross-agent communication, planner/executor/tester/reviewer collaboration, or when no narrower Agent Bus skill clearly fits.

SKILL.md

2.6 KB, 518 tokens by cl100k_base, as published. Nobody here has run it

Agent Bus

Use this as the lightweight entrypoint for the Agent Bus skill family. Classify the request, then load or follow the narrow skill that owns the work.

Routing

  • Register, identify, join as a role, or claim queued messages: use $agent-bus-register.
  • Send/delegate a task, ACK or reply to a message, verify visible delivery, or use pending targets: use $agent-bus-delegate.
  • Create a project team, define role aliases, launch or attach role sessions, or dispatch role-scoped work: use $agent-bus-team.
  • Debug missing agents, stuck sends, hung triggers, unclaimed pending messages, or queued-but-not-visible delivery: use $agent-bus-diagnose.

If a request spans multiple areas, use this order:

  1. Register the current session if identity or inbox state matters.
  2. Create or attach teams if the user asked for role structure.
  3. Delegate work or reply to messages.
  4. Diagnose only if a concrete failure appears.

Global Invariants

  • session_id is the canonical Agent Bus routing identity.
  • agent_id is a non-unique role or name hint.
  • Durable Bus storage and visible Codex thread delivery are separate proof layers.
  • A queued message, pending message, or last_seen update does not prove the target saw the task.
  • When the target is an existing Codex App thread/session and the task should be seen now, prefer Codex App visible delivery after creating the canonical Bus record.
  • When launching new team role threads, prefer $agent-bus-team with team launch --mode codex-app so the controller creates native Codex App threads with codex_app.create_thread.
  • Use pending Bus records for future sessions or stable role aliases that do not have a real thread yet.
  • Do not read Codex auth files, API keys, transcripts, or unrelated private state.
  • Do not edit ~/.codex/config.toml unless the user explicitly asks for installation/configuration work.
  • Avoid repeated resume or codex_app wake attempts; use the narrow skill's timeout and verification rules.

Reporting Standard

Report the concrete identifiers that make the workflow auditable: session_id, agent_id, message_id, correlation_id, team_id, role alias, cwd, trigger, and delivery status when available.

State uncertainty explicitly. For example: "Bus storage is queued; visible thread delivery is not yet confirmed."

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.