What is relaycore AGENTS.md?

A project instruction file for RelayCore, a system used to store durable project rules, decisions, lessons, and other working memory.

Use it to load project context at the start of work, follow required workflows, and save lasting rules and decisions to RelayCore.

It prevents important project knowledge from being lost between sessions or kept only in an agent's temporary memory.

How totooss/relaycore configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to totooss/relaycore. 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/totooss/relaycore/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/totooss/relaycore

Made for: Codex, OpenCode.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/totooss/relaycore/agents-md/github.svg)](https://agentmods.dev/instructions/totooss/relaycore/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/totooss/relaycore/agents-md"><img src="https://agentmods.dev/badge/instructions/totooss/relaycore/agents-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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/totooss/relaycore/agents-md"><img src="https://agentmods.dev/badge/instructions/totooss/relaycore/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 844 This file is loaded in full into every session.

When invoked 844 The same file — it is already loaded in full.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00844	$0.00844
Opus 5.5	$0.00338	$0.00338
Sonnet 5.5	$0.00169	$0.00169
Haiku 4.5	$0.00084	$0.00084

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

Security

Grade A, and why

relaycore AGENTS.md 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 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.

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.

AGENTS.md · 64 lines

How it starts

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

RelayCore Project Instructions

This project uses RelayCore as the only durable project memory layer.

RULES.md is the versioned editorial source for durable methodology and runtime rules. Sync it into RelayCore with relaycore sync-rules --rules-file RULES.md whenever the file changes.

Memory Policy

Treat native model memory as optional, unstable, and non-authoritative.
Do not rely on ChatGPT, Codex, Claude, or any other runtime's built-in memory for project continuity.
Do not store durable project decisions only in native agent memory.
Durable memory for this project means any reusable decision, rule, lesson, rejected option, artifact reference, or workflow state that should survive the current session.
If durable memory is not written to RelayCore, treat it as not stored.

Required Workflow

At task start, call memory_auto_prepare.
If memory_auto_prepare is unavailable, fall back to memory_begin_task and memory_context.
Before planning or implementation, do a short preflight that names the relevant loaded rules, decisions, lessons, and rejected paths that apply to the task.
When a durable fact, decision, rule, or lesson appears, write it with memory_add or memory_propose.
When a decision supersedes or rejects another option, preserve the rejected path and reason through RelayCore memory flows.
Before ending the task, call memory_commit_task.

Required RelayCore Endpoints

MCP: http://127.0.0.1:9090/mcp
Mission Control: http://127.0.0.1:8080/mission-control
Memory Viewer: http://127.0.0.1:8080/mission-control/memories

Multi-Runtime Topology

Treat RelayCore MCP as the shared backend for cross-session and cross-runtime collaboration.
Multiple local runtimes such as Codex, Claude Code, or Hermes can share one relaycore mcp-http process on the same machine.
Mission Control is optional for agent tool calls; it is primarily the operator UI and manual override surface.
Use the same session_id when different runtimes should collaborate on the same task.
Use distinct agent_id values for different runtimes or instances so heartbeats, events, and command handling remain attributable.
If runtimes are on different machines or isolated containers, they must all reach the same shared RelayCore service and canonical database.

Read the full file on GitHub · 64 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.

2mo ago First seen · 64 lines · 844 tokens per session scan A a9c516684867

Subscribe to this mod's changes

relaycore AGENTS.md is an instructions file published in the GitHub repository totooss/relaycore (1 stars, last pushed 3mo ago), licensed MIT. It adds 844 tokens to every session, about $0.0034 per session on Opus 5.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-31.

Memory and context ai claude codex mcp sqlite

relaycore AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
relaycore AGENTS.mdtotooss/relaycore	Instructions file	1	3mo ago	MIT	A	844	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

relaycore: Instructions file for Codex