What is relaycore CLAUDE.md?

Repository instructions that require RelayCore, a durable project-memory service, to store decisions, rules, lessons, and important task results.

Loading relevant memory before work, syncing rule files, recording durable outcomes, and committing task context for future sessions.

They prevent important project context from being lost when a coding session or runtime ends.

How totooss/relaycore configures Claude Code

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

Clone the repo

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

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.

README.md

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

Your own site

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

Your own site · 80×15

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

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

When invoked 634 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.00634	$0.00634
Opus 5.5	$0.00254	$0.00254
Sonnet 5.5	$0.00127	$0.00127
Haiku 4.5	$0.00063	$0.00063

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

Security

Grade A, and why

relaycore CLAUDE.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.

CLAUDE.md · 69 lines

How it starts

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

RelayCore Runtime Contract For Claude

Claude should use RelayCore as the durable memory backend for this repository.

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.

Hard Rules

Native Claude memory is not the project memory system.
Do not assume built-in memory will be available in future sessions.
Do not treat prior chat recall as an acceptable substitute for RelayCore.
Any project decision that should survive the current session must be written to RelayCore.

Minimum Task Sequence

memory_auto_prepare
if unavailable, fall back to memory_begin_task and memory_context
short preflight describing the loaded relevant rules, decisions, lessons, and rejected paths
work
memory_add or memory_propose for durable outcomes
memory_commit_task

What Must Go To RelayCore

accepted decisions
rejected options and reasons
reusable rules
lessons learned
task progress that another runtime may need
artifact references that matter later

What Does Not Need Durable Storage

ephemeral chain-of-thought
transient drafting text
one-off exploration that does not affect future work
formatting chatter that has no project value

Retrieval Guidance

Prefer memory_context with a bounded token budget.
Prefer memory_auto_prepare for startup bootstrap and memory_context for bounded follow-up retrieval.
Prefer compact summaries over dumping full historical transcripts.
Read active decisions, rules, lessons, and relevant rejected knowledge before making new decisions.
If RULES.md changes, sync it into RelayCore before considering the rule change complete.
If the task involves planning, design, implementation, automation, or refactoring, preflight should explicitly verify whether the external-reference baseline rule applies.

Mission Control Boundary

Treat Mission Control command publishing as a manual operator override path.
Default to agent-driven command publication during normal runtime collaboration.
Use the web UI command form only for fallback dispatch, debugging, or session seeding.

Read the full file on GitHub · 69 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 · 69 lines · 634 tokens per session scan A 547c1be05e6e

Subscribe to this mod's changes

relaycore CLAUDE.md is an instructions file published in the GitHub repository totooss/relaycore (1 stars, last pushed 3mo ago), licensed MIT. It adds 634 tokens to every session, about $0.0025 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 CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
relaycore CLAUDE.mdtotooss/relaycore	Instructions file	1	3mo ago	MIT	A	634	Claude Code
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 Claude Code