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/maximyz3d/relaybridge/agents-mdgit clone --depth 1 https://github.com/maximyz3d/relaybridgeWrote 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/maximyz3d/relaybridge/agents-md)<a href="https://agentmods.dev/instructions/maximyz3d/relaybridge/agents-md"><img src="https://agentmods.dev/badge/instructions/maximyz3d/relaybridge/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.00538 | $0.00538 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00108 | $0.00108 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade B, and why
relaybridge AGENTS.md scanned grade B with 1 finding 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 3d 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.
Unrestricted tool accessmediumExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
`start_safe_session(kind:"powershell")` opens a real host PowerShell process. `send_session_input` can execute arbitrary commands under the user's account after host approval. RelayBridge is not a filesystem sandbox. How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RelayBridge Agent Guide
This repository contains RelayBridge, a local Windows PowerShell and AI CLI control plane with browser, REST, and MCP interfaces.
First Call
When connected through MCP, call get_context_bundle first. It returns the bounded handoff packet: health, provider readiness, active work, terminal tails, collaborations, projects, runs, receipts, registry fingerprints, and exact follow-up tools for omitted detail.
Safe Workflow
- Use
bridge_statusandlist_providerswhen you need current readiness. - Use
route_previewbefore spending a hosted provider call. - Use
route_and_askfor one bounded routed provider response. - Use
run_committeefor independent advisory responses from multiple providers. - Use
list_runs,get_run,list_receipts, andget_receiptfor provenance.
For concurrent raw REST calls, generate a unique requestId per call and keep
the direct requestId/invocationId/receiptId tuple together. Never assign a
detached response by selecting the newest receipt.
Terminal Control
start_safe_session(kind:"powershell") opens a real host PowerShell process. send_session_input can execute arbitrary commands under the user's account after host approval. RelayBridge is not a filesystem sandbox.
Use terminal tools only when the user has authorized host execution or when the current task clearly requires it. Prefer read-only discovery and provider routing for analysis.
Environment
Preferred variables:
RELAYBRIDGE_URLRELAYBRIDGE_TOKENRELAYBRIDGE_TOKEN_FILERELAYBRIDGE_CONFIG_FILERELAYBRIDGE_DATA_DIRRELAYBRIDGE_ALLOWED_ROOTS
Legacy PS_BRIDGE_* variables remain supported for older installations.
Security Boundary
RelayBridge binds to 127.0.0.1. The capability token controls REST, WebSocket, and MCP access. Do not print the token in logs, chat, issues, pull requests, or documentation.
Do not commit runtime files:
.bridge-token.state.json.mcp-start.lockdata/node_modules/*.log
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.
- 3d ago First seen · 68 lines · 538 tokens per session scan B 2d3634a0e82a
relaybridge AGENTS.md is an instructions file published in the GitHub repository maximyz3d/relaybridge (0 stars, last pushed 3d ago), licensed MIT. It adds 538 tokens to every session, about $0.0027 per session on Opus 5. A static security scan graded it B with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.