Borrowing it
Nothing to install: this file belongs to bks-lab/open-bridge. 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/bks-lab/open-bridge/main/CLAUDE.mdgit clone --depth 1 https://github.com/bks-lab/open-bridgeWrote 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/bks-lab/open-bridge/claude-md)<a href="https://agentmods.dev/instructions/bks-lab/open-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/bks-lab/open-bridge/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/bks-lab/open-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/bks-lab/open-bridge/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.00624 | $0.00624 |
| Opus 5.5 | $0.00250 | $0.00250 |
| Sonnet 5.5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
open-bridge 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 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.
What it actually says
@AGENTS.md
Claude Code specifics
The canonical, tool-agnostic operating manual for this repo is
AGENTS.md
(Linux-Foundation convention, read natively by Codex/Cursor/Copilot/Gemini). Its size, and
that of everything else a session loads, is reported by python3 scripts/measure-context.py
rather than written down here, where it would go stale. AGENTS.md is inlined
above via @AGENTS.md, so the full manual — session-start gate, rules, task management, agents,
standing orders, commands — is already in your context. This file only adds the
Claude-Code-specific bits.
The project registry (ecosystem.yaml, created at onboarding, per instance) is no longer
@-imported. It is indexed: Phase 1 runs
python3 scripts/context-index.py ecosystem.yaml, which emits the settings verbatim and one
line per repo, customer and workspace; the entry itself arrives with --get <name> when
somebody names one. The registry is the always-on file that grows with the instance rather
than with this repo, and reading it whole meant carrying a paragraph about every project in
order to know that the project exists. Details: docs/context-index.md.
That trade has a real cost worth naming: an @-import is resident for the whole session,
while a Phase 1 read is ordinary conversation and can be compacted away later. The card is
small enough to re-run, and --get is always available; a file large enough to matter here is
too large to keep resident on that argument alone. Keeping the @-import beside a card: gets
neither: measure-context.py fails it as contradiction, since the import loads the file whole.
Onboarding appends further @-imports here as it seeds the live USER files
(e.g. identity/agent/SOUL.md + IDENTITY.md).
Run the Phase-0 session-start gate before responding. Belt-and-suspenders, so the gate
survives even if the import above fails to resolve:
Do not answer the first user message (even "hi", "status", "what can you do") before running Phase 0.
Phase 0 mechanic, inlined here so it works even if @AGENTS.md is silently dropped: detect the
current branch + whether a user/* branch exists + whether bridge-config.yaml is present, and
route accordingly — on the core branch with no user/* and no bridge-config.yaml, trigger the
NEW USER path (/bridge-onboard); otherwise route to the matching state (wrong-branch, orphan,
broken-config, or normal task-management load).
If @AGENTS.md does not resolve in your harness, read AGENTS.md manually before responding.
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.
- 2d ago Changed · +3 lines · +73 tokens per session 8e673d51c9cf
- 1mo ago Changed d698eeca140c
- 1mo ago First seen · 38 lines · 551 tokens per session scan A 0a4e6e47be7d
open-bridge CLAUDE.md is an instructions file published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed yesterday), licensed MIT. It adds 624 tokens to every session, about $0.0025 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.