agent-bus-collab

Files (2)

• SKILL.md
• agent_bus.py · scripts/

SKILL.md (first lines)

# Agent Bus Collab

Use this skill when Codex needs to coordinate with Grok or another local agent through Agent Bus MCP.

## Session Persistence

When the user invokes this skill, continue using it for the rest of the current session unless the user explicitly turns it off or redirects away from bus coordination.

While active:

- check the relevant bus topic before making shared-area claims or edits;
- post meaningful status, handoffs, and blockers to the bus;
- read peer replies from the bus before treating them as durable coordination state;
- keep using the repository, not the bus, for durable artifacts.

## Contract

Agent Bus is a coordination ledger. The repository remains the source of truth for durable research artifacts, code, evidence, and claims.

Use the bus for:

- status;
- task claims;
- handoffs;
- objections;
- readiness checks;
- coordination questions;
- paths to repo artifacts.

Do not use the bus as the durable location for research evidence, proofs, experiment output, or final reports. Put those in the repo and link the path from the bus.

## Identities

Use stable agent names:

- Codex: `codex`
- Grok: `grok`

Runtime and model details belong inside the message body when relevant, not in the bus identity.

## Message Shape

Use this lightweight structure unless the message is genuinely tiny:

```markdown
agent: codex
runtime: Codex Desktop
model: GPT-5

## Status
...

## Claim / Observation
...

## Evidence
...

## Request / Handoff
...

## Boundary
...
```

For questions and replies, use Agent Bus `message_type='question'` and `message_type='answer'` when the tool exposes that field. Use `reply_to` when answering a specific bus message.

## Start Of Session

Before claiming or editing work in an active shared area:

1. Resolve or create the relevant topic.
2. Join as `codex`.
3. Replay from sequence 0 or from the last known cursor.
4. Check for recent claims, blockers, or handoffs.
5. Post a short claim/status before making overlapping edits.

For the standing readiness topic:

```text
topic name: agent-bus-readiness
topic id: 2f6aae70cd
```

## Tool Use

Prefer native Agent Bus MCP tools when they are exposed in the current Codex session:

- `ping`
- `topic_create`
- `topic_list`
- `topic_resolve`
- `topic_join`
- `cursor_reset`
- `sync`
- `topic_presence`
- `messages_search`

If the native Agent Bus tools are not surfaced but the local server is installed, use the bundled helper script as the explicit transport to the same MCP server. This is not a substitute protocol; it calls the installed Agent Bus MCP server over stdio.

Helper:

```bash
python /Users/velocityworks/.codex/skills/agent-bus-collab/scripts/agent_bus.py --help
```

The helper uses:

```text
uvx --from agent-bus-mcp==0.5.0 agent-bus
AGENT_BUS_DB=/Users/velocityworks/.agent_bus/agent_bus.sqlite
```

## Common Commands

Replay a topic:

```bash
python /Users/velocityworks/.codex/skills/agent-bus-collab/scripts/agent_bus.py history agent-bus-readiness

From zfifteen/skills-catalog, MIT.

More from zfifteen/skills-catalog