Borrowing it
Nothing to install: this file belongs to wolverin0/wezbridge. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/wolverin0/wezbridge/main/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/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.
<a href="https://agentmods.dev/instructions/wolverin0/wezbridge/claude-md"><img src="https://agentmods.dev/badge/instructions/wolverin0/wezbridge/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01710 | $0.01710 |
| Opus 5.5 | $0.00684 | $0.00684 |
| Sonnet 5.5 | $0.00342 | $0.00342 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
wezbridge CLAUDE.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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scoped instructions; read for applicable authority, execution and verification rules.
Wezbridge in Claude Code
Read AGENTS.md for the shared project contract and DOCS-MAP.md before following document references. The selected orchestration owner is determined by the operator and live identity, not by the provider of this session.
- Claude-specific tools do not define Fleet authority. Preserve the task's existing authorization and repository ownership.
- Use the existing daemon for durable wake delivery and recovery. A session-local Monitor is not a replacement for that service.
- Prefer
a2a_send; verify the returned delivery status and avoid duplicate message effects. npm testruns the project suite with the required WezTerm test double. There is no build script.- Core MCP tools use the WezTerm CLI directly. The headless daemon on port 4200 provides background services; verify it with
bridge_health, not a request to its intentionally absent home page. - Operational configuration and recovery procedures are in
docs/operations.md; modules/endpoints are mapped indocs/repo-layout.md. - Historical architecture and old suite counts are evidence of their dated checkpoints, not current runtime status or permission.
GitNexus — Code Intelligence
This project is indexed by GitNexus as wezbridge (73420 symbols, 203951 relationships, 300 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
If any GitNexus tool warns the index is stale, run
npx gitnexus analyzein terminal first.
Always Do
- MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run
gitnexus_impact({target: "symbolName", direction: "upstream"})and report the blast radius (direct callers, affected processes, risk level) to the user. - MUST run
gitnexus_detect_changes()before committing to verify your changes only affect expected symbols and execution flows. - MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
- When exploring unfamiliar code, use
gitnexus_query({query: "concept"})to find execution flows instead of grepping. It returns process-grouped results ranked by relevance. - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use
gitnexus_context({name: "symbolName"}).
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.
- 1mo ago Changed 6ed296fe60fb
- 1mo ago Changed · -67 lines · -1,545 tokens per session 99dcc25ffeab
- 1mo ago Changed · -58 lines · -1,087 tokens per session fb2479cb1894
- 2mo 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 1mo ago), licensed MIT. It adds 1,710 tokens to every session, about $0.0068 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-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).
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.
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).
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 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).
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.