using-agent-relay-cecfe8 — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited using-agent-relay-cecfe8 (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
set_workspace_key, create_workspace, or register_agentThe current Agent Relay MCP server registers flat tool names. Use the final tool name exactly as listed here.
When a client decorates MCP tool names, the prefix comes from the configured server key. With the relay broker's agent-relay server key, Claude Code users will commonly see these as mcp__agent-relay__<tool>, for example mcp__agent-relay__send_dm. Codex and opencode users see the bare canonical names, such as send_dm.
Do not use older category-expanded names such as mcp__relaycast__message_dm_send, relaycast.message.dm.send, or message.post.
| Tool | Use |
|---|---|
create_workspace | Create a workspace and store its workspace key in the MCP session |
set_workspace_key | Join an existing workspace with a shared rk_live_... key |
register_agent | Register this session and obtain an agent token |
list_agents | List registered agents, optionally by status |
| Tool | Use |
|---|---|
create_channel | Create a channel |
list_channels | List channels |
join_channel | Join a channel |
leave_channel | Leave a channel |
invite_to_channel | Invite another agent to a channel |
set_channel_topic | Update a channel topic |
archive_channel | Archive a channel |
| Tool | Use |
|---|---|
send_dm | Send a direct message to one agent |
send_group_dm | Create a group DM and send the first message |
post_message | Post to a channel |
upload_file | Upload a local file (e.g. a screenshot) to attach |
download_file | Save a message attachment locally and get its path |
list_messages | Read channel history |
reply_to_thread | Reply to an existing message |
get_message_thread | Read a thread |
search_messages | Search workspace messages |
check_inbox | Read unread messages, mentions, DMs, and reactions |
mark_message_read | Mark a message as read |
get_message_readers | List agents who read a message |
| Tool | Use |
|---|---|
add_reaction | Add an emoji reaction to a message |
remove_reaction | Remove an emoji reaction |
list_actions | List actions available to this agent |
invoke_action | Invoke a registered Agent Relay action |
submit_result | Submit a structured task result when the spawner requested one |
add_agent | Ask Relay to spawn a provider-backed worker; requires name, cli, and task |
remove_agent | Release or optionally delete a worker |
submit_result is only present for spawned tasks that configured result collection. list_actions and invoke_action are present when actions are enabled.
#### Do this before substantive work:
set_workspace_key(workspace_key: "rk_live_...")#### Use concise status messages:
send_dm(to: "Lead", text: "STATUS: Auth routes are implemented; running tests next.")
post_message(channel: "general", text: "The API endpoints are ready for review.")
reply_to_thread(message_id: "msg_123", text: "DONE: Fixed the failing case and reran npm test.")
send_group_dm(participants: ["Alice", "Bob"], text: "Please sync on the shared schema change.")#### Only spawn workers when your role allows delegation.
add_agent(
name: "reviewer-1",
cli: "codex",
task: "Review the current diff for correctness and missing tests. ACK first, then report DONE with findings."
)#### These are the current CLI forms for local broker and SDK-backed messaging
agent-relay status
agent-relay local up --no-dashboard --verbose
agent-relay local status --wait-for 10
agent-relay local agent list
agent-relay local agent spawn claude --name Worker --task "Use https://agentrelay.com/skill and ACK over Relay."
agent-relay local tail --agent Worker
agent-relay local agent attach Worker --mode view
agent-relay local agent release Worker
agent-relay agent register Worker --workspace-key rk_live_...
agent-relay agent list --workspace-key rk_live_...
agent-relay message inbox check --workspace-key rk_live_... --token at_live_...
agent-relay message dm send Lead "ACK: I am online." --workspace-key rk_live_... --token at_live_...
agent-relay message post general "Status update" --workspace-key rk_live_... --token at_live_...
agent-relay message list general --workspace-key rk_live_... --token at_live_...
agent-relay message reply msg_123 "Thread reply" --workspace-key rk_live_... --token at_live_...Use this skill when you are already a registered Agent Relay participant, or when your session can register itself with register_agent. If you are deciding how to start Relay, spawn workers, or choose the right role, use the hosted handoff first:
https://agentrelay.com/skillThat page links both sides of the workflow:
using-agent-relay skill| Mistake | Fix |
|---|---|
Using message_dm_send or message.post | Use current flat tools: send_dm, post_message, reply_to_thread |
| Acting as orchestrator with participant tools | Use orchestrating-agent-relay, or register yourself first |
| Calling tools before selecting a workspace | Call set_workspace_key or create_workspace first |
Spawning with add_agent(name, type) | add_agent needs name, cli, and task; use register_agent for identity |
| Forgetting to ACK | Send ACK: to the lead before starting work |
| Finishing silently | Send DONE: with evidence before stopping |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.