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/rayline-ai/rayline/agents-mdgit clone --depth 1 https://github.com/rayline-ai/raylineWrote 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/rayline-ai/rayline/agents-md)<a href="https://agentmods.dev/instructions/rayline-ai/rayline/agents-md"><img src="https://agentmods.dev/badge/instructions/rayline-ai/rayline/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.00958 | $0.00958 |
| Opus 5 | $0.00479 | $0.00479 |
| Sonnet 5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
rayline 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rayline Agent Notes
CLAUDE.md is a symlink to this file. Keep rules short, current, and
repo-specific.
Crate Boundaries
rayline-cli: user commands and CLI UX.rayline-daemon:rldprocess orchestration.rayline-proxy: proxying, TLS interception, CA handling, request routing.rayline-injector: process/environment injection.rayline-adapter: adapter protocol translation.rayline-local-router: static routing policy and endpoint selection.rayline-hf,rayline-llama,rayline-metrics: model/cache/runtime support.
Keep protocol and routing logic in shared crates. Do not duplicate it in CLI handlers. Prefer focused modules over growing the existing large CLI/proxy files.
CLI Contracts
- Use the current routing flags in new docs, tests, and examples:
--local,--via proxy|env, and--route all|subagents. - Treat
--local-router,--no-proxy, and--routing-mode ...as deprecated compatibility aliases only. --localmeans local static routing without hosted auth.--via envis cloud-only and must not be combined with local inference or selective subagent routing.- Local routing defaults to
--route subagents; cloud routing defaults to--route all. - Use
--router-config-pathwhenroutes.subagentsis meant to constrain the transparent proxy allowlist. Do not rely onRAYLINE_ROUTER_CONFIGalone for that allowlist. rayline topshould work for proxy-mode launches when metrics can bind. Metrics bind failures are best-effort and must not break proxy data flow.
Commands
cargo build --workspace --locked
cargo build --release -p rayline-cli -p rayline-daemon --locked
cargo +1.88.0 fmt --all -- --check
cargo +1.88.0 test --workspace --locked -- --test-threads=1
cargo +1.88.0 clippy --workspace --all-targets --locked -- -D warnings
cargo audit --file Cargo.lock
cargo deny --locked check advisories bans licenses sources
git diff --check
Use the pinned Rust toolchain. Run targeted checks while iterating and the relevant full gate before handoff.
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.
- 4d ago First seen · 91 lines · 958 tokens per session scan A e6380ac4ac7a
rayline AGENTS.md is an instructions file published in the GitHub repository rayline-ai/rayline (23 stars, last pushed 2d ago), licensed Apache-2.0. It adds 958 tokens to every session, about $0.0048 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
turso AGENTS.md
Instructions for tursodatabase/turso, covering turso agent guidelines, quick reference, testing, running tests and test organization.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
azure-sdk-for-rust resourcemanager.instructions.md
Instructions for Azure/azure-sdk-for-rust, a project described as: This repository is for the active development of the Azure SDK for Rust. For consumers of the SDK we recommend visiting Docs.rs and looking up the docs for any of libraries in the SDK.
agentgateway copilot-instructions.md
Copilot instructions for agentgateway/agentgateway: Do not check for, speculate about, or report compilation errors during code review. Compilation diagnostics from review are frequently incorrect; rely on CI to detect and report compilation failures.
terminal-browser AGENTS.md
AGENTS.md instructions for zenbu-labs/terminal-browser, a project described as: A browser inside your terminal.
mq commit.instructions.md
Instructions for harehare/mq: Use the following format for commit messages.