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-syncgit 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-sync)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/bridge-sync"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-sync/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-sync"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-sync.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.00089 | $0.00997 |
| Opus 5.5 | $0.00036 | $0.00399 |
| Sonnet 5.5 | $0.00018 | $0.00199 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
bridge-sync 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 22d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Sync — Batch end-of-sprint upstream sync
/bridge-sync is the wide-net complement to /promote and /contribute.
| Skill | Granularity | Use case |
|---|---|---|
/promote |
per-commit | "promote this batch of recent commits" |
/contribute |
per-file | "scan for upstream-worthy files, adapt, PR" |
/bridge-sync |
per-sprint | "push EVERYTHING pending to both upstreams now" |
Read the referenced file ONLY when triggered.
When to use
- End of a work-sprint, ready to publish all upstream-worthy changes at once
- After a refactor that touched many CORE+org files — manual cherry-pick is tedious
- When
/promotehas been deferred for days and there's a backlog - When you want both
bks-lab/open-bridgeand your org overlay updated in one operation
NOT for:
- A single commit (
/promoteis leaner) - File-level adaptation work (
/contribute --adaptdoes that) - USER-only changes (those stay local)
Arguments
| Argument | Effect | Default |
|---|---|---|
(none) |
Full sync to both upstreams | — |
--dry-run |
Show routing matrix, don't push | false |
--repo open-bridge |
Sync only to open-bridge | both |
--repo <your-bridge> |
Sync only to your org overlay | both |
--since <ref> |
Sync commits since this ref (default: last sync tag) | last sync |
--no-scrub |
Disable open-bridge scrubbing (DANGER — only for emergency) | false |
Prerequisites
- Current branch must be
user/*. Refuses ondevelopment/main. bridge-config.yaml.upstreams[]defines BOTH upstreams.git remotehasorigin(your fork) +upstream(typically<your-org>/<your-bridge>).- For open-bridge sync:
ghCLI authenticated with cross-fork PR rights.
Decision Tree
User wants to...
├── Full sync (default) → references/workflow.md
├── Dry-run / preview routing → references/workflow.md (stop after Step 4)
├── Sync only one repo → references/workflow.md § --repo override
├── Configure scrub patterns → rules/promote-safety.md per-repo blocklists
├── Tag the sync point → references/workflow.md § sync-tag
└── PR merge fails after squash-merge → references/pr-recovery-patterns.md
(stale-ancestor / non-fast-forward)
What ships with it
4 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.
- 22d ago Changed · -2 lines · -29 tokens per session 6d887b31e03f
- 1mo ago First seen · 93 lines · 118 tokens per session scan A 33b098705823
bridge-sync is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 997 once invoked, about $0.0004 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.
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.
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.
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"…