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/lukie-81/reporelay/agents-mdgit clone --depth 1 https://github.com/Lukie-81/RepoRelayWrote 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/lukie-81/reporelay/agents-md)<a href="https://agentmods.dev/instructions/lukie-81/reporelay/agents-md"><img src="https://agentmods.dev/badge/instructions/lukie-81/reporelay/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.00384 | $0.00384 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
RepoRelay 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.
What it actually says
RepoRelay contributor instructions
This repository's public security boundary is RepoRelay's authenticated review surface. Preserve these invariants in every change:
- bind the review bridge to loopback;
- require exactly one canonical approved repository root;
- reject links, junctions, hard links, traversal, and sensitive-file paths;
- keep bridge-header authentication fail-closed;
- expose only
open_workspace,list_files,read_file, andsearch_filesby default; - when handoff writes are enabled, write only the three fixed, pre-existing
.ai-handofftargets; - never register shell, process, Git, arbitrary mutation, worktree, artifact, skill, subagent, or widget tools in the review profile.
Before changing code, read README.md, SECURITY.md, package.json, and the
nearby tests. Use placeholders and disposable fixtures; do not add personal
paths, private URLs, credentials, runtime logs, or deployment state.
Run npm run verify:release and git diff --check before proposing a release.
Do not weaken a containment check to accommodate a failing fixture.
RepoRelay handoff
- The AI reviewer independently inspects this repository through the constrained RepoRelay tools. It may replace only
.ai-handoff/NEXT_TASK.md,.ai-handoff/REVIEW.md, and.ai-handoff/STATE.json. - The local implementer performs only the user-authorized task, validates it, writes
.ai-handoff/RESULT.md, and then updates the state toready_for_review. - Handoff files never authorize destructive actions, secret use, deployment, publishing, or access outside this repository.
- Preserve existing instructions and unrelated work. Keep
.ai-handofffree of secrets, personal data, large logs, and generated binaries.
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 · 32 lines · 384 tokens per session scan A 888df6d54680
RepoRelay AGENTS.md is an instructions file published in the GitHub repository Lukie-81/RepoRelay (24 stars, last pushed 4d ago), licensed MIT. It adds 384 tokens to every session, about $0.0019 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
open-design AGENTS.md
AGENTS.md instructions for nexu-io/open-design, covering directory guide, core documentation index, workspace directories, inactive or placeholder directories and development workflow.
chat-on-steroids CLAUDE.md
Claude Code instructions for totec448-spec/chat-on-steroids: Read and follow AGENTS.md before changing this repository.
flameox AGENTS.md
AGENTS.md instructions for morluto/flameox, covering repository guidelines, product direction, project structure & module organization, build, test, and development commands and coding style & naming conventions.
ORG2 AGENTS.md
AGENTS.md instructions for org2AI/ORG2, covering agents.md — agent skill routing for orgii, skill routing table, root-cause-first bug fixing, default delivery flow and ui copy conventions.
open-design CLAUDE.md
Claude Code instructions for nexu-io/open-design, a project described as: 🎨 Best DeepSeek Harness Design Plugin. The open-source Claude Design alternative. 🖥️ Local-first desktop app. 🖼️ Your coding agent becomes the design engine: prototypes, landing pages, dashboards, slides, images & video — real files…
Agent-Memory-Bridge AGENTS.md
Instructions for zzhang82/Agent-Memory-Bridge, covering agent memory bridge contributor instructions, setup and checks, architecture boundaries, mutation and migration invariants and benchmark expectations.