Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bks-lab/open-bridgenpx agentmods add skills/bks-lab/open-bridge/bridge-overlayWrote 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/skills/bks-lab/open-bridge/bridge-overlay)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/bridge-overlay"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-overlay/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/skills/bks-lab/open-bridge/bridge-overlay"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-overlay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.04062 |
| Opus 5.5 | $0.00029 | $0.01625 |
| Sonnet 5.5 | $0.00014 | $0.00812 |
| Haiku 4.5 | $0.00007 | $0.00406 |
Grade A, and why
bridge-overlay 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 4d 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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Overlay — subscribe to an org's config bundle
An org overlay is a git repo an organisation publishes so its members'
Bridges can share config without each person hand-copying files. It mirrors a
flat tree of files (tree/<path> → <path>), every file scope: org,
declared by a root overlay.manifest.yaml. /overlay is the consumer side:
it subscribes, materializes COPIES under a lockfile, and keeps them in sync.
It is the mirror-image of the push skills:
| Skill | Direction | Unit |
|---|---|---|
/promote · /bridge-sync |
push your scope:org/core commits up to an upstream |
commits |
/overlay |
pull an org's published config down into your repo | manifest-declared files |
Read the referenced file ONLY when triggered.
When to use
- An org gives you a git URL: "subscribe your Bridge to our overlay"
- You want the org's shared contexts / projects / mandants / accounts / org skills materialized locally and kept current
- You already subscribed and want to pull updates (
sync), preview them (diff), re-materialize offline (apply), check freshness (status), or end the subscription (remove)
NOT for:
- Publishing an overlay (that's the org's job — see
references/authoring.md) - Pushing YOUR changes upstream (
/promote,/bridge-sync) - One-off file copies with no ongoing subscription (just copy the file)
What an overlay carries
An overlay ships an org's scope: org building blocks as a flat tree/ mirror —
config AND tools, so one git-URL is a complete org bridge, not just config:
| Group | Path | Kind | Gate |
|---|---|---|---|
| Contexts / projects / mandants / accounts | workflow/ · identity/ |
config | batch-confirm |
| Remotes / shared infra | infra/ |
config | batch-confirm |
| Org rules | rules/org/** |
rule | batch-confirm |
| Org skills (complete) | skills/<name>/** |
skill | one [y] per skill folder |
| Org sub-agents | .claude/agents/<name>.md |
agent | [y] per file |
| Ecosystem fragment | ecosystem.<org>.yaml |
ecosystem-fragment | batch-confirm + @import |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed · +5 lines 4d641077cb83
- 13d ago Changed 420eefc71a06
- 1mo ago Changed · -9 lines · -118 tokens per session 99617c4db3bc
- 1mo ago Changed 93b548957a3d
- 1mo ago Changed · +10 lines c0d35ca158dd
- 1mo ago First seen · 239 lines · 190 tokens per session scan A 8a18a52a607b
bridge-overlay is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 4,062 once invoked, about $0.0003 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 skills, from other repositories
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
pr-shepherding
Monitor PR lifecycle from creation through merge including CI monitoring, review comment handling, thread resolution, and merge readiness verification.
team-pr
Use for opening PRs only on explicit request. Never infer from passed verification. Includes project terms, evidence, and risk.