relay: Instructions file for Claude Code

CLAUDE.md

relay CLAUDE.md is an instructions file for Claude Code from future-beat/relay. It costs 6,298 tokens per session, scanned A, original, MIT.

A project instruction file that tells a coding agent how the Relay support-ticket service is built, including its technology, constraints, and deployment setup.

In plain words
What is it for?
Use it when working on Relay’s Python service, ticket-handling agent, live dashboard, deployment, or automated checks.
Why use it?
It gives the agent the project context needed to make changes that fit the existing service and avoid breaking its interfaces or operating limits.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Claude Code; reads ~/.codex paths.

This is future-beat/relay's own configuration. It tells Claude Code how to work on relay itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything relay configures →

Reuse

Borrowing it

Nothing to install: this file belongs to future-beat/relay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/future-beat/relay/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/future-beat/relay

Made for: Claude Code.

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 relay CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/future-beat/relay/claude-md/github.svg)](https://agentmods.dev/instructions/future-beat/relay/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/future-beat/relay/claude-md"><img src="https://agentmods.dev/badge/instructions/future-beat/relay/claude-md/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 relay CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/future-beat/relay/claude-md"><img src="https://agentmods.dev/badge/instructions/future-beat/relay/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6,298 This file is loaded in full into every session.
When invoked 6,298 The same file — it is already loaded in full.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.06298 $0.06298
Opus 5.5 $0.02519 $0.02519
Sonnet 5.5 $0.01260 $0.01260
Haiku 4.5 $0.00630 $0.00630

Measured 2mo ago against content hash 20d68911e6d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

relay CLAUDE.md scanned grade A with 1 finding 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 2mo 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.

Makes network callslowCapability

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

- Used by: External clients (curl, browser dashboard, `scripts/demo.sh`).
CLAUDE.md · 251 lines

How it starts

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

Project

Relay — Remaster

Relay is an AI support-triage agent built as a production service: it receives support tickets over a REST API, works each one autonomously with a hand-written agent loop on the Claude API (customer lookup, classification, grounded doc search, reply or escalation), and streams its reasoning as SSE. This milestone remasters the existing v1 into a portfolio showpiece: production-hardened, with real semantic retrieval and a polished live dashboard.

Core Value: A visitor hitting the live demo sees a credible, safe, observably-real AI agent service — impressive to read and watch, cheap to keep running.

Constraints

  • Budget: Live demo must stay cheap — single Fly machine, min_machines_running=0, per-run cost budget retained; Voyage usage is index-once + tiny per-query cost
  • Tech stack: Python/FastAPI/SQLite/Claude API retained; no orchestration framework — the visible hand-written loop is a feature
  • Deploy: One container, no build step, existing Fly.io + GitHub Actions pipeline keeps working
  • Compatibility: SSE event contract and MCP tool surface stay backward compatible where practical; evals must keep passing

Technology Stack

Languages

  • Python 3.11+ (requires-python >=3.11 in pyproject.toml) - entire application (src/relay/)
  • HTML/CSS/JS (inline, no build step) - src/relay/main.py (DASHBOARD_HTML constant, a single-page dashboard with vanilla fetch/setInterval polling)
  • Markdown - knowledge base content in kb/*.md, consumed by keyword search tool
  • Bash - scripts/demo.sh (demo/smoke script)

Runtime

  • CPython 3.11+ (project floor) / 3.12 (CI, Docker) / 3.14 (local venv)
  • ASGI server: uvicorn[standard]>=0.30 (pyproject.toml), started via uvicorn relay.main:app (Dockerfile CMD, README quick start)
  • pip with pyproject.toml (PEP 621 style), build backend hatchling
  • No lockfile present (no requirements.txt, poetry.lock, or uv.lock) — dependency versions are floor-pinned only (>=)

Read the full file on GitHub · 251 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. 2mo ago First seen · 251 lines · 6,298 tokens per session scan A 20d68911e6d3

Subscribe to this mod's changes

relay CLAUDE.md is an instructions file published in the GitHub repository future-beat/relay (0 stars, last pushed 14d ago), licensed MIT. It adds 6,298 tokens to every session, about $0.0252 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

relay CLAUDE.md compared with instructions from other repositories

relay CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
relay CLAUDE.mdfuture-beat/relayInstructions file014d agoMITA6,298Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode