Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/agentworkforce/relay/using-agent-relaynpx skills add AgentWorkforce/relay --skill using-agent-relaygit clone --depth 1 https://github.com/AgentWorkforce/relayWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00085 | $0.02350 |
| Opus 5 | $0.00043 | $0.01175 |
| Sonnet 5 | $0.00017 | $0.00470 |
| Haiku 4.5 | $0.00009 | $0.00235 |
Grade A, and why
using-agent-relay scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Agent Relay
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/skill
That page links both sides of the workflow:
- outside orchestrators and human drivers use
orchestrating-agent-relay - spawned or registered participants use this
using-agent-relayskill
Role Check
Use this skill if:
- you were spawned into a Relay team
- the prompt gave you a workspace key or Relay identity
- you can call
set_workspace_key,create_workspace, orregister_agent - you need to ACK, report status, DM peers, post to channels, or check inbox
Do not use this as the outside orchestrator playbook. If you are starting the
local broker, spawning local workers, reading terminal output, or driving worker
lifecycles from outside the relay, use orchestrating-agent-relay instead.
Current MCP Tool Names
The 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. Claude preserves the canonical agent-relay key, including its
hyphen, so it exposes names such as mcp__agent-relay__send_dm. The old
mcp__relaycast__* prefix belongs only to legacy configurations. In every case,
the canonical tool name is the flat suffix, 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.
Workspace and Identity
| 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 |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 257 lines · 85 tokens per session scan A 370aefd4ab94
using-agent-relay is a skill published in the GitHub repository AgentWorkforce/relay (806 stars, last pushed 2d ago), licensed Apache-2.0. It adds 85 tokens to every session and 2,350 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
reskin
Author a NEW skin for the reskinnable-demo app. A skin is a self-contained domain plugin under src/skins/ / that implements the frozen Skin contract (src/shell/skin-contract.ts) to swap the app's entire experience — brand, theme, layout, pages, tools, data, and agent — as a live sales demo. Use when the user says "add…
copilotkit-channels
Use for the CODE half of a managed Intelligence Channel with Slack or Microsoft Teams: customising the Channel a CLI-scaffolded project already ships, or — for a project the CLI did not generate — writing the Channel declaration, the long-running host, and the awaited activation call. Teams provider setup is in scope…
setup-slack-channel
Use for the PROVIDER half of getting a locally running CopilotKit Channels agent to answer in Slack, when no Slack app exists yet — setting up a Channels bot in Slack for the first time, creating the Slack app and its tokens, attaching it to a managed Intelligence Channel, or when a Channel reports setuprequired, sits…
runtime
@copilotkit/runtime — mount a fetch-native CopilotRuntime on any JS server, wire middleware, pick an AgentRunner, instantiate BuiltInAgent (Factory Mode with TanStack AI is the preferred default) or plug in any of 12 external agent frameworks (Mastra, LangGraph, CrewAI Crews/Flows, PydanticAI, ADK, LlamaIndex, Agno…
copilotkit-develop
Use when building AI-powered features with CopilotKit v2 -- adding chat interfaces, registering frontend tools, sharing application context with agents, handling agent interrupts, and working with the CopilotKit runtime.
copilotkit-integrations
Use when wiring an external agent framework (LangGraph, CrewAI, PydanticAI, Mastra, ADK, LlamaIndex, Agno, Strands, Microsoft Agent Framework, or others) into a CopilotKit application via the AG-UI protocol.