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 skills add bks-lab/open-bridge --skill bridge-promotegit 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/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.00147 | $0.01476 |
| Opus 5 | $0.00073 | $0.00738 |
| Sonnet 5 | $0.00029 | $0.00295 |
| Haiku 4.5 | $0.00015 | $0.00148 |
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 9d 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 — 112 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 |
scope: personal |
the upstream with scope: personal only (your personal overlay) |
Cherry-pick + PR to that repo |
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.
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.
- 9d 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 (8 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session and 1,476 once invoked, about $0.0007 per session on Opus 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
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.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
maintenance-orchestration
Technical debt management including branch cleanup, doc verification, TODO scanning, and dependency auditing.
worktree-isolation
Manage git worktree lifecycle for safe, isolated parallel development.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.