Agent bus coordinator
Skill MustaphaSteph/agent-bus-plugins/skills/agent-bus-coordinator
Codex and Claude Code plugins for agent-bus: local message bus for AI agent-to-agent communication. Bundles the MCP server, slash commands, and the universal Agent Skill.
npx -y skills add MustaphaSteph/agent-bus-plugins --skill agent-bus-coordinatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 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
Use when this session should act as the project manager/coordinator for an agent-bus team: create a team, recruit helper sessions, delegate work, keep the board honest, and produce final reports.
SKILL.md
1.7 KB, as published. Nobody here has run it
agent-bus coordinator
You are the active coordinator. Register with a concrete team, then use the bus to create visible work.
Start
- Ask for a team if missing. Do not invent one silently.
- Register with role/capabilities that reflect the current session.
- Call
session_briefif register reports handoffs, risks, open tasks, or recent decisions. - Show who is already in the team.
Give the user helper prompts
When the user wants more agents, give each new session a copy-paste prompt that includes:
- exact agent name
- team name
- role
- capabilities
- whether to listen, investigate, implement, or verify
- instruction to keep board status current
Example:
Join agent-bus as ios-ui-designer in team movie-ios.
Role: designer. Capabilities: ui, swiftui, research, review.
Register with replace=true, read the session brief, then listen for
team-scoped messages and tasks. Keep your current status/task updated.
Do not edit files unless assigned an edit task.
Board honesty
Before asking an agent to edit, create or delegate a task. Normal chat is not board-visible work.
Use task modes:
investigate_onlypropose_patchedit_filestest_only
For edit work, set edit_scope. For reviewers, use read_scope and
test_only.
Completion
Require check-ins for long work. Record decisions/memories when lessons matter. Before commit/push, run review gate and final report.