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 skills add gabrielmoreira/agent-skills-mirror --skill using-agent-relaygit clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirrorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/using-agent-relay)<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/using-agent-relay"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/using-agent-relay/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/using-agent-relay"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/using-agent-relay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $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 7d 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.
This is a copy
100% identical to using-agent-relay — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 7d ago First seen · 257 lines · 85 tokens per session scan A 370aefd4ab94
using-agent-relay is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. 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. It is 100% identical to using-agent-relay, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.