Borrowing it
Nothing to install: this file belongs to Lukie-81/RepoRelay. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Lukie-81/RepoRelay/main/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/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.
<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="Reviewed on agentmods" width="80" 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.1 | $0.00384 | $0.00384 |
| Opus 5.5 | $0.00154 | $0.00154 |
| Sonnet 5.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 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.
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.
- 2mo 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 (29 stars, last pushed 2mo ago), licensed MIT. It adds 384 tokens to every session, about $0.0015 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.