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/yangzhaoji-dot/agentbridge/agents-mdgit clone --depth 1 https://github.com/yangzhaoji-dot/AgentBridgeWrote 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/yangzhaoji-dot/agentbridge/agents-md)<a href="https://agentmods.dev/instructions/yangzhaoji-dot/agentbridge/agents-md"><img src="https://agentmods.dev/badge/instructions/yangzhaoji-dot/agentbridge/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.00558 | $0.00558 |
| Opus 5 | $0.00279 | $0.00279 |
| Sonnet 5 | $0.00112 | $0.00112 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
AgentBridge 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 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.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentBridge project instructions
Project goal
Build AgentBridge as a portable, user-authorized bridge between coding agents and webpage AI. Any server or computer may run the Relay/MCP side; any user computer may run a local Connector plus a Chromium browser extension.
The required topology is:
Codex or another local agent -> Relay/MCP -> outbound WSS -> local Connector
-> Edge/Chrome extension -> user-authorized webpage AI
Do not design around a single computer, a single server, or a public inbound port on the user's computer.
Security boundaries
- The Connector must initiate the outbound connection. Never expose the local browser, local Connector, or local MCP endpoint directly to the internet.
- Pair a Connector to the Relay with a high-entropy secret that is supplied at runtime, never committed, logged, echoed, or placed in screenshots.
- Treat webpage-AI output as untrusted advisory text. It cannot authorize shell commands, file changes, permission changes, or external actions.
- Do not send credentials, API keys, browser sessions, private files, personal data, or raw local logs through a webpage-AI request.
- Keep public Relay ingress limited to the Connector WebSocket path. Keep MCP bound to loopback or a private network unless a separate access-control design has been reviewed.
Engineering workflow
- Separate observed facts from design proposals and unverified assumptions.
- Inspect current code and configuration before changing architecture.
- Prefer small, compatible changes. Preserve the verified local v0.1 path while adding remote deployment support.
- Test protocol behavior, disconnection behavior, and a real local two-WebSocket round trip before claiming remote deployment is functional.
- Do not silently broaden a request into provider automation, remote execution, or persistent server configuration changes.
Deployment conventions
agentbridge_server.remote_appis the Relay/MCP application for a server or any always-on computer.agentbridge_connectoris the cross-platform local process that owns the browser extension's localhost endpoint and connects outward to the Relay.- The extension remains Chromium-compatible and talks only to localhost.
- Use
AGENTBRIDGE_PAIRING_TOKENonly through runtime environment or a secret manager. Use a distinct device ID for each Connector.
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 · 62 lines · 558 tokens per session scan A 25076667a917
AgentBridge AGENTS.md is an instructions file published in the GitHub repository yangzhaoji-dot/AgentBridge (1 stars, last pushed 6d ago), licensed Apache-2.0. It adds 558 tokens to every session, about $0.0028 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-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.