agent-bridge AGENTS.md

Instructions for AgentBridge, a setup that lets this coding agent collaborate with another AI agent from a parallel session. They describe when to collaborate, how the agents differ, and how to exchange messages.

In plain words
What is it for?
Use them when splitting architecture, code review, research, debugging, or implementation work between two agents. They explain how to start collaboration and use the available review-graph tools.
Why use it?
They help decide when a second perspective or parallel work would improve a complex task. They also define how responsibilities and communication should be handled.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/raysonmeng/agent-bridge/agents-md
Clone the repo
git clone --depth 1 https://github.com/raysonmeng/agent-bridge

Made for: Codex, OpenCode.

Per session 726 This file is loaded in full into every session.
When invoked 726 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00726 $0.00726
Opus 5 $0.00363 $0.00363
Sonnet 5 $0.00145 $0.00145
Haiku 4.5 $0.00073 $0.00073

Measured 2d ago against content hash c9d7be95b287, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agent-bridge 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 2d 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 · 68 lines

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.

AgentBridge — Multi-Agent Collaboration

You are working in a multi-agent environment powered by AgentBridge. Another AI agent (Claude, by Anthropic) is available in a parallel session on this machine. Communication happens via AgentBridge MCP tools — Claude has reply and get_messages tools.

When to collaborate vs. work solo

  • Collaborate when the task benefits from a second perspective, parallel execution, or capabilities the other agent has.
  • Work solo for simple, self-contained tasks where the coordination overhead isn't worth it.
  • When in doubt, propose a task split to Claude rather than doing everything yourself.

Capability comparison

Capability Codex (you) Claude
Sandboxed code execution Yes No
Reproduce & verify bugs Strong Limited
Architecture & planning Moderate Strong
Code review & analysis Strong Strong
Web search & docs Limited Yes
File editing & refactoring Yes (via sandbox) Yes (via tools)

How to start collaborating

  1. When you receive a complex task, proactively propose a division of labor.
  2. State what you'll handle and what you'd like Claude to take on.
  3. Ask for Claude's agreement or counter-proposal before proceeding.
  4. After task completion, cross-review each other's work.

MCP Tools: code-review-graph

IMPORTANT: This project has a knowledge graph. ALWAYS use the code-review-graph MCP tools BEFORE using Grep/Glob/Read to explore the codebase. The graph is faster, cheaper (fewer tokens), and gives you structural context (callers, dependents, test coverage) that file scanning cannot.

When to use graph tools FIRST

  • Exploring code: semantic_search_nodes or query_graph instead of Grep
  • Understanding impact: get_impact_radius instead of manually tracing imports
  • Code review: detect_changes + get_review_context instead of reading entire files
  • Finding relationships: query_graph with callers_of/callees_of/imports_of/tests_for
  • Architecture questions: get_architecture_overview + list_communities

Read the full file on GitHub · 68 lines

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. 2d ago First seen · 68 lines · 726 tokens per session scan A c9d7be95b287

Subscribe to this mod's changes

agent-bridge AGENTS.md is an instructions file published in the GitHub repository raysonmeng/agent-bridge (315 stars, last pushed 3d ago), licensed MIT. It adds 726 tokens to every session, about $0.0036 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.