setting-up-relayfile

setting-up-relayfile is a skill for Claude Code, Codex from gabrielmoreira/agent-skills-mirror. It costs 107 tokens per session (2,628 once invoked), scanned C, a copy of setting-up-relayfile, MIT.

A setup guide for relayfile, which presents services such as Notion, Linear, Slack, and GitHub as files on a local mounted folder. Agents can then read and write provider data through the filesystem instead of calling each service's API directly.

In plain words
What is it for?
Use it to mount provider data, read or update pages and issues through files, choose integration backends, and diagnose a broken mount.
Why use it?
It explains the first-time setup and recovery steps needed to connect these services, select integrations, and keep the mounted files working.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it to mount provider data, read or update pages and issues through files, choose integration backends, and diagnose a broken mount.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile
Install

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.

Any agent
npx skills add gabrielmoreira/agent-skills-mirror --skill setting-up-relayfile
Clone the repo
git clone --depth 1 https://github.com/gabrielmoreira/agent-skills-mirror

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for setting-up-relayfile

README.md
[![agentmods](https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile/github.svg)](https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile)
Your own site
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile/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.

agentmods 80×15 button for setting-up-relayfile

Your own site · 80×15
<a href="https://agentmods.dev/skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile"><img src="https://agentmods.dev/badge/skills/gabrielmoreira/agent-skills-mirror/setting-up-relayfile.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,628 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00107 $0.02628
Opus 5 $0.00053 $0.01314
Sonnet 5 $0.00021 $0.00526
Haiku 4.5 $0.00011 $0.00263

Measured 7d ago against content hash c9d4cd69d06c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

setting-up-relayfile scanned grade C with 2 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf ~/relayfile-mount

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sS -X POST "https://agentrelay.com/cloud/api/v1/workspaces/<id>/integrations/connect-session" \
Origin

This is a copy

100% identical to setting-up-relayfile — 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.

mirrors/repos/AgentWorkforce@relay/.agents/skills/setting-up-relayfile/SKILL.md · 224 lines

How it starts

The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Overview

Relayfile mounts a provider (Notion, Linear, Slack, GitHub, and other adapter-backed integrations) as ordinary files on disk so an agent can read and write through the filesystem instead of calling APIs. This skill is the canonical setup recipe. Follow it top-to-bottom for first-time setup; jump to Recovering from breakage if a working mount has gone wrong.

When to use this skill

  • An agent needs read access to a provider (e.g., "summarize this Notion database").
  • An agent needs to write back to a provider (e.g., "post a review on this Notion page", "update this Linear issue").
  • A human is setting up a mount before delegating work to an agent.
  • A mount stopped reflecting changes and you need to diagnose where.

What you get

After setup, files appear under <local-dir>/<provider>/...:
~/relayfile-mount/notion/
├── databases/
│   ├── <slug>--<id>/
│   │   ├── metadata.json     ← database schema (read-only)
│   │   └── pages/
│   │       ├── <slug>--<id>.json     ← page metadata
│   │       └── <slug>--<id>/
│   │           ├── content.md        ← page body (READ + WRITE)
│   │           └── blocks/<id>.json  ← raw Notion block tree
└── pages/                            ← top-level pages (not in a database)

Prerequisites

  • Recent relayfile CLI on $PATH. Verify: relayfile --help should list setup, integration, writeback, and the integration available / integration search / integration set-metadata subcommands.
  • A modern macOS or Linux shell with jq for JSON inspection. AWS CLI access is optional and only needed for internal cloud log diagnostics.
  • Network access to agentrelay.com/cloud (cloud control plane), api.relayfile.dev (relayfile API), connect.nango.dev (Nango OAuth), and Composio connect endpoints when using --backend composio.

Step 1 — Run setup (interactive happy path)

```bash
relayfile setup \
  --provider notion \
  --workspace my-agent \
  --local-dir ~/relayfile-mount \
  --no-open

Read the full file on GitHub · 224 lines

Changes

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.

  1. 7d ago First seen · 224 lines · 107 tokens per session scan C c9d4cd69d06c

Subscribe to this mod's changes

setting-up-relayfile is a skill published in the GitHub repository gabrielmoreira/agent-skills-mirror (17 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 2,628 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). It is 100% identical to setting-up-relayfile, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories