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 instructions/priorlabs/relarena/agents-mdgit clone --depth 1 https://github.com/PriorLabs/relarenaWrote 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/instructions/priorlabs/relarena/agents-md)<a href="https://agentmods.dev/instructions/priorlabs/relarena/agents-md"><img src="https://agentmods.dev/badge/instructions/priorlabs/relarena/agents-md.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.01258 | $0.01258 |
| Opus 5 | $0.00629 | $0.00629 |
| Sonnet 5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
relarena 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
relarena — agent notes
Start with the README for what the package is and how a run works.
This repo is public
Everything committed here is published under Apache-2.0 — code, docs, and
baseline_results/ alike. Nothing may reference Prior Labs–internal
infrastructure, systems, names, or paths. This applies to everything pushed
to the remote, not just tracked files: commit messages, branch names, and PR
text included.
Adding or changing a model
Read docs/adding-a-model.md first. Model development
is two things: the model folder (layout, fit/predict contract and its
datatypes, search-space choices, shared-code placement, optional dependencies,
vendoring, tests) and — for methods with expensive CPU pre-processing — a
public cache-warm script. models/lightgbm/ is the smallest complete example
to copy.
Refactor-friendly structure rules
Keep the contract/tuning core, models, predictive interface, and benchmark evaluation layers cleanly separated:
- Import through the public API: external-facing names are re-exported in
relarena/__init__.py(or a subpackage__init__.py), and docs, examples, and tests use those paths. Underscore-prefixed modules are internal and may move without notice. - Respect the layering: model packages and
userdb/import the generic core (model,registry,search_space,tuner, split types) and the shared infrastructure (featurization/) — never each other, and never the benchmark-onlyevaluation/subpackage.models/_shared/is for code shared between models; nothing outsidemodels/imports it. - Keep generic and benchmark-specific code in separate modules: anything
touching
relbench.datasets/relbench.tasksor data checksums is benchmark code and doesn't belong inmodel/tuner/search_space. - Heavy optional deps are lazy-imported inside
fitbehind extras; no import-time side effects beyond explicitregister_modelcalls.
macOS: run tests / CLI with OMP_NUM_THREADS=1
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.
- today Changed · +8 lines · +76 tokens per session f3ba91c837d0
- 5d ago First seen · 86 lines · 1,182 tokens per session scan A 4453c6a82f20
relarena AGENTS.md is an instructions file published in the GitHub repository PriorLabs/relarena (57 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,258 tokens to every session, about $0.0063 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 instructions, from other repositories
chdb AGENTS.md
Instructions for chdb-io/chdb, covering agents.md — chdb, 1. fully lazy execution architecture, 2. natural execution triggering (explicit calls prohibited), 3. unified architecture, simplicity first and 4. testing principles.
stata-code CLAUDE.md
Claude Code instructions for brycewang-stanford/stata-code, covering claude.md — stata-code project notes, communication, release coordination, pypi / testpypi trusted publishing — what to know and recovery: invalid-publisher failure.
LogLead CLAUDE.md
Instructions for EvoTestOps/LogLead, covering claude.md, project overview, environment setup, common commands and architecture.
streamlit e2e_playwright.instructions.md
Instructions for streamlit/streamlit, covering streamlit e2e tests, test structure, key fixtures and utilities, external test mode and url handling (no localhost hardcoding).
streamlit AGENTS.md
AGENTS.md instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.
StatsPAI CLAUDE.md
Claude Code instructions for brycewang-stanford/StatsPAI, covering claude.md — statspai, 1. 项目定位, 2. 仓库结构, 3. 设计原则 and 4. 代码规范.