Skip to content
Back to skills

Peer Messaging

ASecurity

Cross-session Claude Code instance messaging via claude-peers-mcp broker

  • 15 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 12, 2026
ai-agentsbashsql

Works with

  • claude code
  • terminal
  • mcp

Security analysis

A96/100
  • mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned September 12, 2026

npx -y skills add baekenough/second-brain --skill peer-messaging --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Peer Messaging?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Peer Messaging
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/baekenough-peer-messaging/badge)](https://www.skillsdirectory.com/skills/baekenough-peer-messaging)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: peer-messaging
description: Cross-session Claude Code instance messaging via claude-peers-mcp broker
scope: core
user-invocable: false
---

# Peer Messaging Skill

## Purpose

Enables cross-session coordination between multiple Claude Code instances through the claude-peers-mcp broker. Complements Agent Teams (R018, intra-session) with inter-session messaging.

## Scope Clarification

| Scope | Mechanism | Tools | Use Case |
|-------|-----------|-------|----------|
| Intra-session agents | Agent Teams (R018) | TeamCreate, SendMessage | Single session multi-agent collaboration |
| Cross-session instances | claude-peers-mcp | list_peers, send_message | Multi-terminal/project real-time coordination |
| Cross-session memory | claude-mem | save_memory, search | Async memory persistence |

> **Important**: R018's `SendMessage` and claude-peers-mcp's `send_message` are different tools with different scopes. Do not confuse them.

## MCP Tool Mapping

| Tool | Purpose | oh-my-customcode Scenario |
|------|---------|---------------------------|
| `list_peers` | Discover active Claude instances | `omcustom:status` system overview |
| `send_message` | Send message to peer | Cross-project workflow coordination |
| `set_summary` | Broadcast current task summary | DAG cross-project step sync |
| `check_messages` | Read incoming messages | Receive coordination signals |

## Use Cases

### Multi-Project Workflow
Terminal A runs `auto-dev` on project-1; Terminal B works on dependent project-2. Peers coordinate via messages when blocking dependencies are resolved.

### Cross-Project QA
Share test infrastructure state between projects running concurrent test suites.

### DAG Bridge
`dag-orchestration` cross-project steps can use peer messaging for synchronization (currently impossible without this tool).

## Setup

```bash
# Install broker (optional MCP server)
npm install -g claude-peers-mcp

# Add to MCP config
claude mcp add claude-peers-mcp -- npx claude-peers-mcp
```

## Integration

- Works with R018 Agent Teams (different scope, complementary)
- Works with claude-mem (async vs sync messaging)
- Works with `omcustom:status` (peer discovery)
- Broker runs on localhost:7899 (SQLite-backed)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…