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-promoteWrote 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-promote)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/bridge-promote"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-promote/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-promote"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-promote.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.00071 | $0.01765 |
| Opus 5.5 | $0.00028 | $0.00706 |
| Sonnet 5.5 | $0.00014 | $0.00353 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
bridge-promote 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Promote — Scope Routing
Routes commits from user/* to the right upstream based on scope:
frontmatter (or path inference). See CLAUDE.md § Tier Model.
| Commit scope | Goes to | How |
|---|---|---|
scope: core (or unset, on CORE-allowlist path) |
the upstream with scope: core (e.g. bks-lab/open-bridge:main) plus any org/personal overlay that also carries it |
Cherry-pick to local development, then PR to the OSS upstream |
scope: org |
the upstream with scope: org only (your org overlay, e.g. <your-org>/<your-bridge>:development) |
Cherry-pick + PR to that repo, unless it is a flat mirror (below): then refuse and export |
scope: personal |
the upstream with scope: personal only (your personal overlay) |
Same as org: cherry-pick + PR, or refuse and export for a flat mirror |
scope: user / private |
stays local on user/{name} |
No-op |
Destination selection is by SCOPE, never by role: alone. For a
commit/file of scope S, the destination is the bridge-config.yaml.upstreams[]
entry whose scope: field == S — core→the scope: core upstream,
org→the scope: org upstream, personal→the scope: personal upstream.
Two upstreams may now share role: org-overlay (an org overlay and a
personal overlay), so role no longer identifies a unique destination.
FAIL-CLOSED guard (mandatory). Before routing, count the upstreams with
role: org-overlay. If that count is > 1 and the routing would still
pick any destination by role (rather than by a matching scope: field),
ABORT — do not guess. Message: "Ambiguous routing: N upstreams carry
role: org-overlay but a destination is being chosen by role. Route by
upstreams[].scope (org→scope: org, personal→scope: personal) instead.
Aborting rather than risk sending personal PII to the org overlay or customer
content to the personal repo."
HARD GATE — personal upstream stays disabled for real promotes until proven.
Do not enable the scope: personal upstream for a non---dry-run promote until
a --dry-run routing matrix shows every scope: personal file routed to the
personal upstream and every scope: org file routed to the org upstream,
with zero cross-routes. Until that dry-run is green, treat scope: personal
files as local-only.
FLAT-MIRROR GUARD (mandatory, per overlay destination). An overlay repo
that carries overlay.manifest.yaml is read by scripts/overlay.py only below
its defaults.source_root (tree/ when unset). A cherry-pick writes the same
path it had here, so the file lands at the overlay's repo root and no consumer
ever sees it, without any error. Before routing (workflow Step 0b), per overlay
destination, against the ref Step 0 fetched:
python3 scripts/overlay-export.py --check-ref {name}/{branch}
Any non-zero exit means REFUSE that destination (3: flat mirror, 2: the ref
does not resolve, so the fetch failed or the name is wrong): do not
cherry-pick, re-apply, or open a PR there, not even for scope: core commits. Tell the user to build the mirror
instead with python3 scripts/overlay-export.py --target <overlay checkout> --scope <tier> --dry-run (then without --dry-run), after pulling any
colleague PR against tree/ back first. Other destinations still ship. Recipe:
docs/org-overlays.md § Authoring an overlay.
If you don't have an org overlay configured, only scope: core commits
get promoted; scope: org / scope: personal commits stay on your user branch.
Read the referenced file ONLY when triggered.
What ships with it
1 file 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 · +20 lines 0b203636aebe
- 11d ago Changed · +2 lines 858e7b87adf5
- 1mo ago Changed · -6 lines · -76 tokens per session 1838cd990eef
- 1mo ago First seen · 112 lines · 147 tokens per session scan A 6cdd6bb8d9c2
bridge-promote is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 1,765 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
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
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…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
beevibe-pre-task-setup
Cold-start git workspace setup for a fresh beevibe task. Use at the start of a session whose intent has a block but NO or block — i.e. the first dispatch of this task. Checks for an existing repo clone, pulls the base branch if present (clone if missing), prunes any per-task worktrees from earlier tasks whose work has…