bridge-awareness

bridge-awareness is a skill for Claude Code from PatilShreyas/claude-code-session-bridge. It costs 38 tokens per session (1,613 once invoked), scanned B, original, MIT.

A guide for agent sessions connected through Claude Bridge, a system that lets separate coding-agent sessions exchange messages and ask one another questions.

In plain words
What is it for?
Use it when checking with another session, sending a question to a peer, listening for requests, or finding the identity of the current bridge session.
Why use it?
It helps an agent discover connected peers and communicate with them while keeping the relevant session context.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the session-bridge plugin — 1 skill, 1 command, 1 hook shipped together

Good fit Use it when checking with another session, sending a question to a peer, listening for requests, or finding the identity of the current bridge session.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add PatilShreyas/claude-code-session-bridge
Claude Code
/plugin install session-bridge

Made for: Claude Code.

Or install session-bridge, the plugin that ships this one along with the rest of its 1 skill, 1 command, 1 hook.

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 bridge-awareness

README.md
[![agentmods](https://agentmods.dev/badge/skills/patilshreyas/claude-code-session-bridge/bridge-awareness/github.svg)](https://agentmods.dev/skills/patilshreyas/claude-code-session-bridge/bridge-awareness)
Your own site
<a href="https://agentmods.dev/skills/patilshreyas/claude-code-session-bridge/bridge-awareness"><img src="https://agentmods.dev/badge/skills/patilshreyas/claude-code-session-bridge/bridge-awareness/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 bridge-awareness

Your own site · 80×15
<a href="https://agentmods.dev/skills/patilshreyas/claude-code-session-bridge/bridge-awareness"><img src="https://agentmods.dev/badge/skills/patilshreyas/claude-code-session-bridge/bridge-awareness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,613 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00038 $0.01613
Opus 5 $0.00019 $0.00807
Sonnet 5 $0.00008 $0.00323
Haiku 4.5 $0.00004 $0.00161

Measured 9d ago against content hash 20c2f2f29207, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

bridge-awareness 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 9d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

find ~/.claude/session-bridge/sessions/$MY_SESSION/inbox -name "*.json" -exec jq -r 'select(.type == "ping") | "\(.metadata.fromProject) (\(.from))"' {} \; 2>/dev/null | sort -u
plugins/session-bridge/skills/bridge-awareness/SKILL.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bridge Awareness

You are connected to other Claude Code sessions via the Claude Bridge plugin. This skill defines how you communicate with peer agents.

Getting your session ID: Always use bash "${CLAUDE_PLUGIN_ROOT}/scripts/get-session-id.sh" to get your session ID. This works even if you've cd'd into a subdirectory. In listen mode, use TO_ID from the message output instead (even more reliable).

Querying Peers

When the user asks you to communicate with a peer — whether via /bridge ask, or in natural language like "ask the library about...", "check with the peer", "what did the other session change", etc. — do this:

  1. Get your session ID. If no bridge exists yet, auto-register first:
    MY_SESSION=$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/get-session-id.sh" 2>/dev/null) || MY_SESSION=$(bash "${CLAUDE_PLUGIN_ROOT}/scripts/register.sh")
    
    Then find connected peers:
    find ~/.claude/session-bridge/sessions/$MY_SESSION/inbox -name "*.json" -exec jq -r 'select(.type == "ping") | "\(.metadata.fromProject) (\(.from))"' {} \; 2>/dev/null | sort -u
    
    If no connected peers found but the user specified a peer by name or session ID, connect first:
    BRIDGE_SESSION_ID=$MY_SESSION bash "${CLAUDE_PLUGIN_ROOT}/scripts/connect-peer.sh" "<peer-id>"
    
  2. If multiple peers, pick the most relevant one (by project name) or ask the user.
  3. Send the query and capture the message ID:
    MSG_ID=$(BRIDGE_SESSION_ID=$MY_SESSION bash "${CLAUDE_PLUGIN_ROOT}/scripts/send-message.sh" <peer-id> query "Your question here")
    
  4. Tell the user: "Asking [peer-project-name]..."
  5. Wait for the response (blocks up to 90 seconds):
    bash "${CLAUDE_PLUGIN_ROOT}/scripts/bridge-receive.sh" "$MY_SESSION" "$MSG_ID" 90
    
  6. When the response arrives, read it carefully:
    • If it's a direct answer, use it to continue the user's task — update code, fix errors, apply migrations, etc.
    • If the peer is asking a follow-up question (they need more info from you), answer their question and send a new query with your answer + the original question. Then wait again with bridge-receive.sh.
  7. Continue this back-and-forth until you get a final answer, then apply it.

Read the full file on GitHub · 110 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. 9d ago First seen · 110 lines · 38 tokens per session scan B 20c2f2f29207

Subscribe to this mod's changes

bridge-awareness is a skill published in the GitHub repository PatilShreyas/claude-code-session-bridge (67 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 1,613 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories