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/setting-up-relayfilenpx skills add AgentWorkforce/relay --skill setting-up-relayfilegit clone --depth 1 https://github.com/AgentWorkforce/relayWrote 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/agentworkforce/relay/setting-up-relayfile)<a href="https://agentmods.dev/skills/agentworkforce/relay/setting-up-relayfile"><img src="https://agentmods.dev/badge/skills/agentworkforce/relay/setting-up-relayfile.svg" alt="Measured on agentmods" 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 | $0.00107 | $0.02628 |
| Opus 5 | $0.00053 | $0.01314 |
| Sonnet 5 | $0.00021 | $0.00526 |
| Haiku 4.5 | $0.00011 | $0.00263 |
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 4d 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" \ 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
relayfileCLI on$PATH. Verify:relayfile --helpshould listsetup,integration,writeback, and theintegration available/integration search/integration set-metadatasubcommands. - A modern macOS or Linux shell with
jqfor 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
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.
- 4d ago First seen · 224 lines · 107 tokens per session scan C c9d4cd69d06c
setting-up-relayfile is a skill published in the GitHub repository AgentWorkforce/relay (813 stars, last pushed today), licensed Apache-2.0. 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
lime-governance
Govern Lime legacy cleanup, fact-source convergence, current/compat/deprecated/dead classification, and guardrails.
lime-quality-workflow
Choose Lime validation commands for GUI, command/bridge, config, version, and PR-readiness changes.
lime-release-workflow
准备并执行 Lime 发版；覆盖版本号、发布说明、产物清理、验证门禁、commit、tag 和推送。.
image_generate
Skill "image_generate" from limecloud/lime, covering 工作目标, 执行规则 and 输出规则（固定）.
brand-persona-knowledge-builder
将品牌定位、价值观、受众画像、语气风格、内容样例、危机回应和表达禁区，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的品牌人设知识库。适用于用户要求“整理品牌人设”“沉淀品牌口吻”“把品牌资料变成可复用语气库”“维护品牌 persona pack”的场景。.
brand-product-knowledge-builder
将品牌产品资料、规格参数、卖点证据、FAQ、价格权益、竞品区别和合规边界，整理成符合 Agent Knowledge v0.6 document-first 标准、可被 AI 安全调用的产品资料知识库。适用于用户要求“整理产品知识库”“沉淀产品 FAQ”“把品牌产品资料变成项目资料”“维护产品资料包”的场景。.