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/wolverin0/wezbridge/claude-mdgit clone --depth 1 https://github.com/wolverin0/wezbridgeWrote 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/wolverin0/wezbridge/claude-md)<a href="https://agentmods.dev/instructions/wolverin0/wezbridge/claude-md"><img src="https://agentmods.dev/badge/instructions/wolverin0/wezbridge/claude-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.04342 | $0.04342 |
| Opus 5 | $0.02171 | $0.02171 |
| Sonnet 5 | $0.00868 | $0.00868 |
| Haiku 4.5 | $0.00434 | $0.00434 |
Grade A, and why
wezbridge CLAUDE.md scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`http://127.0.0.1:4200/` returns 404 — that's intentional. The daemon is headless. Verify it's up with `curl http://127.0.0.1:4200/api/panes`, or from any session call the `bridge_health` MCP tool. It binds loopback only How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wezbridge (v3.5.0)
Status 2026-07-02 (v3.5.0): focused MCP server, not the abandoned theorchestra orchestrator. Zero npm dependencies. The browser dashboard, the orchestrator-worker pane, the React/Vite v3 build, and the orchestra-goose Tier-2 recipes were removed and preserved at the
omniclaude-pre-rollbackgit tag (commitacd3460). If you're a Claude Code session reading this, you are a regular dev session — there is no orchestrator-worker convention anymore.v3.5.0 highlights:
send_prompt/a2a_sendnow VERIFY submission (read the input box back, retry enter, returnsubmitted) — the manual follow-upsend_key("enter")rule is obsolete on v3.5+ servers.spawn_sessionstarts FRESH sessions by default (continue: trueto opt back into--continue), and gainsagent: claude|codex|shell+model.read_outputgains delta/cursor polling.wait_for_idle/spawn_sessionno longer block the MCP event loop.
What this repo is
An MCP server that exposes mcp__wezbridge__* tools so any Claude Code or Codex CLI session can spawn, prompt, read, and discover other sessions running in WezTerm panes. The core MCP tools talk to the WezTerm CLI directly — they do NOT require the :4200 daemon. Only auto_handoff calls the daemon (/api/panes/:id/auto-handoff); every other tool works with the daemon down. The :4200 HTTP daemon is a separate headless backend (SSE events, telegram-streamer, session-snapshot crash-restore, grades) — start it with npm run dashboard when you want those. Call bridge_health to see, in one shot, whether wezterm is reachable, the daemon is up, and the snapshot watcher is armed.
Security (v3.4.3): the daemon binds
127.0.0.1only. To expose it on a LAN setWEZBRIDGE_BIND(e.g.0.0.0.0) — aWEZBRIDGE_API_TOKENthen becomes mandatory or the daemon refuses to start.
What this repo is NOT
- Not a browser dashboard (the v2.3-v3.1 dashboard UI was deprecated 2026-05-03 and removed in v3.2.1; see
src/DEPRECATED.md) - Not an autonomous orchestrator (the orchestrator-worker pane / JSON-tick / vault-driven escalation system was reverted 2026-05-03)
- Not a hosted multi-agent platform
- Not a replacement for Claude Code / Codex / wezterm
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 · 243 lines · 4,342 tokens per session scan A 16ae1c7437d7
wezbridge CLAUDE.md is an instructions file published in the GitHub repository wolverin0/wezbridge (1 stars, last pushed 15d ago), licensed MIT. It adds 4,342 tokens to every session, about $0.0217 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
kungfu copilot-instructions.md
Copilot instructions for kungfu-systems/kungfu: Read and follow AGENTS.md before proposing or running changes. It is the shared agent router for this repository, including the canonical Shifu development and build entrypoint.
superset CLAUDE.md
Claude Code instructions for superset-sh/superset, a project described as: Superset is an agentic IDE to orchestrate 100+ coding agents in parallel. Run any agent with your own subscription.
agents CLAUDE.md
Instructions for eloylp/agents, covering claude.md, project overview, directory structure, config model and build & run.
growmos AGENTS.md
Instructions for codician-team/growmos: This repository keeps a knowledge graph in .growmos/ (entities, typed relations, provenance, profiles, a journal). It is the shared world model that survives context windows. Treat it as memory you read at the start of work and write to as you develop. Zero-config commands.
ideate AGENTS.md
Instructions for paultyng/ideate, covering agents.md, build features as mcp tools first, ui second, when to add ui and pattern.
omk CLAUDE.md
Claude Code instructions for dmae97/omk, covering claude.md, precedence (read this first), omk runtime map (what you're operating inside), this repo: open-multi-agent-kit / omk monorepo and build / test / check commands.