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-contributegit 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-contribute)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/bridge-contribute"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-contribute.svg" alt="Measured on agentmods" 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.00165 | $0.00899 |
| Opus 5 | $0.00082 | $0.00449 |
| Sonnet 5 | $0.00033 | $0.00180 |
| Haiku 4.5 | $0.00016 | $0.00090 |
Grade A, and why
bridge-contribute 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 8d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Contribute — give improvements back upstream
This is the skill the open-bridge community uses to feed features and
improvements back: it turns work on your user/* branch into a clean,
reviewed pull request against bks-lab/open-bridge (or your org's
overlay repo) — and it refuses to ship anything the content-safety
gate flags. Protecting your own customer names, personal data, and
internal paths is a hard gate, not a checkbox.
Read the referenced file ONLY when triggered.
Arguments
| Argument | Effect | Default |
|---|---|---|
(none) |
Scan and categorize all contributable files | — |
{path} |
Analyze a specific file or directory | — |
--adapt |
Generalize org-specific content before contributing | false |
--repo <name> |
Only consider candidates for one destination | all |
Decision Tree
User wants to...
├── Scan branch for contributions → references/workflow.md
├── Contribute a specific file/dir → references/workflow.md ({path})
├── Adapt/generalize content first → references/workflow.md § Adapt mode
├── Promote whole commits by scope → use the bridge-promote skill (/promote)
└── Questions about scope routing → CLAUDE.md § tier model
Safety (MANDATORY — the reason this skill exists)
No PR is created until the two-layer gate passes for the exact outgoing file set:
python3 scripts/no-scrub-leak.py {files}—scripts/no-scrub-leak.pyis a shared repo-root utility shipped with the Bridge repo itself, not a file inside this skill's own directory. It checks universal classes (absolute user paths, key/token shapes, merge-conflict markers) plus your own roster fromscripts/leak-patterns-internal.txt(local-only, never shipped — you maintain your customer/PII regexes there; the shipped scanner cannot know them).- The per-destination blocklist scan from
rules/promote-safety.md— the OSS upstream uses the strictest list.
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.
- 8d ago First seen · 85 lines · 165 tokens per session scan A efb5a45ceb94
bridge-contribute is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed yesterday), licensed MIT. It adds 165 tokens to every session and 899 once invoked, about $0.0008 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.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.