peerbridge-mcp: Instructions file for Codex

AGENTS.md

peerbridge-mcp AGENTS.md is an instructions file for Codex, OpenCode from Hoylon/peerbridge-mcp. It costs 200 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for PeerBridge, a local-first control room for coding tasks, reviews, evidence, and private remote work across desktop, mobile, and remote connections.

In plain words
What is it for?
Use them when modifying PeerBridge interfaces or backend controls, especially commands, approvals, remote access, credentials, and release checks.
Why use it?
They keep permissions, audit records, transport behavior, and privacy rules consistent while the project changes.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is Hoylon/peerbridge-mcp's own configuration. It tells Codex and OpenCode how to work on peerbridge-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything peerbridge-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Hoylon/peerbridge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Hoylon/peerbridge-mcp/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Hoylon/peerbridge-mcp

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for peerbridge-mcp AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hoylon/peerbridge-mcp/agents-md/github.svg)](https://agentmods.dev/instructions/hoylon/peerbridge-mcp/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/hoylon/peerbridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hoylon/peerbridge-mcp/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.

agentmods 80×15 button for peerbridge-mcp AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hoylon/peerbridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/hoylon/peerbridge-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 200 This file is loaded in full into every session.
When invoked 200 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00200 $0.00200
Opus 5.5 $0.00080 $0.00080
Sonnet 5.5 $0.00040 $0.00040
Haiku 4.5 $0.00020 $0.00020

Measured 1mo ago against content hash 90541f36b492, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

peerbridge-mcp 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 1mo 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.

AGENTS.md · 16 lines

What it actually says

PeerBridge Agent Instructions

  • Read DESIGN.md before changing any local, remote-desktop, or mobile interface.
  • Preserve the same room, task, Agent, dispatch, audit, and permission semantics on every viewport and transport.
  • A visible command must call a real bounded backend operation. Never add decorative send, interrupt, approval, file, voice, shell, or power controls.
  • Tailscale Serve is the production browser transport. The Tailcat integration is visible and enabled by default; its managed Port, SSH, and Exit node process must remain client-key allow-listed, locally switchable, and independently authenticated. A Tailcat address is transport discovery, not PeerBridge authorization.
  • Keep credentials, local context imports, provider diagnostics, and project databases out of Git and rendered snapshots.
  • Run focused tests, the full suite with a fresh temporary root, desktop/mobile visual checks, and a secret scan before publication.
Changes

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.

  1. 1mo ago First seen · 16 lines · 200 tokens per session scan A 90541f36b492

Subscribe to this mod's changes

peerbridge-mcp AGENTS.md is an instructions file published in the GitHub repository Hoylon/peerbridge-mcp (242 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 200 tokens to every session, about $0.0008 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-09-03.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens