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 rules/prakrititz/relaybrain/relaygit clone --depth 1 https://github.com/prakrititz/relayBrainWhat 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.00619 | $0.00619 |
| Opus 5 | $0.00309 | $0.00309 |
| Sonnet 5 | $0.00124 | $0.00124 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cursorrules — 97% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Relay (auto-installed)
This project uses Relay for cross-agent memory. Do not ask the user to configure agent files manually.
Every session — read first: .relay/AGENT_BOOTSTRAP.md
| Phase | Action |
|---|---|
| Session start | Read .relay/relay_context.md (handoff). Never paste raw transcripts. |
| After agent work | You update .relay/*.md from compile_brief.md (stop hook triggers this) |
| Background sync | relay watch . keeps memory.json + compile_brief.md fresh |
| Not installed? | Run relay add . or relay init in project root |
Stop hooks: Cursor, Claude Code, Codex, Copilot CLI, Antigravity — installed by relay add / relay init.
Relay MCP: relay_room_brief, locks, chat history — installed into each agent's MCP config by relay add.
Relay pseudo-commands (user chat)
These are not built-in slash commands. They are a project convention — phrases the user types so agents recognize Relay intent.
When the user sends any of these phrases (with or without a leading /), treat them as Relay instructions — not casual chat:
| User says | You do |
|---|---|
/relay update or relay update |
relay sync . → relay compile . → read .relay/compile_brief.md → update .relay/project.md, current_task.md, decisions.md, failures.md → relay context . → confirm "Relay updated." |
/relay context or relay context |
Read .relay/relay_context.md (run relay context . first if stale). Summarize handoff briefly. |
/relay ask or relay ask |
Call Relay MCP tool relay_room_brief (MCP server relay). Required on Cursor, Claude Code, Codex, Copilot CLI, and Antigravity — not a terminal command for the human. Summarize teammate chat, code edits, locks, and file-sync notes. Tell the user before you edit shared files. If relay MCP is missing, say so and suggest relay add . + agent restart (do not ask the user to run relay ask). |
/relay init or relay init |
Run relay init in project root if .relay/ missing; else confirm already installed. |
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 · 41 lines · 619 tokens per session scan A e9abdcfa8b71
relay is a cursor rule published in the GitHub repository prakrititz/relayBrain (31 stars, last pushed 3d ago), licensed MIT. It adds 619 tokens to every session, about $0.0031 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 cursor rules, from other repositories
app_layer_rules
App layer (API) contract for FastAPI endpoints in backend/apps. Parse/validate input, call services, map domain errors to HTTP, return JSONResponse on success.
frontend_overview_rules
Frontend overview - directory structure, layer responsibilities, and dependency rules.
service_layer_rules
Service layer implements core business logic orchestration; raise custom exceptions; no HTTP handling.
hook_layer_rules
Hook layer rules for custom React hooks and state management.
page_layer_rules
Page layer rules for Next.js App Router pages and layouts.
type_layer_rules
Type layer rules for TypeScript type definitions and interfaces.