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 agentmods add skills/bks-lab/open-bridge/workloadnpx skills add bks-lab/open-bridge --skill workloadgit clone --depth 1 https://github.com/bks-lab/open-bridgeWhat 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 | $0.00248 | $0.09368 |
| Opus 5 | $0.00124 | $0.04684 |
| Sonnet 5 | $0.00050 | $0.01874 |
| Haiku 4.5 | $0.00025 | $0.00937 |
Grade A, and why
workload 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 2d 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 — 607 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workload
One declared run, on one machine, with an owner. The declaration in
workflow/workloads/<id>.yaml is the source of truth; the unit file on the
machine is an artifact and may be rebuilt from the declaration at any time.
The engine is skills/workload/engine/ behind the shim skills/workload/workload.sh.
The data is the declaration plus _schema.yaml and _template.yaml next to it.
Nothing instance specific lives in the code: hosts come from infra/remotes/,
paths and prefixes from the workloads: block of bridge-config.yaml.
Guard
workloads.enabled must not be false in bridge-config.yaml. A missing block
means defaults, never a crash. A false refuses every subcommand with exit 3
and names the key and the file it read.
reconcile --notify speaks through the program declared in
workloads.notify_via, never through a name this skill knows:
workloads:
notify_via:
command: ["~/bin/my-notifier", "--subject", "{what}", "--host", "{where}",
"--action", "{todo}"]
detail: ["--body", "{detail}"] # appended only when there is detail
Substitution is per argv element, so a value with a space stays one argument.
With no notify_via, --notify sends nothing and says so, naming the key: an
alarm path this skill invented would be a dependency the repository does not
ship.
Commands
workload list [--host H] [--kind K] [--runtime R] [--owner O] [--scope S] [--retired] [--json]
workload show <id> [--render] [--json]
workload validate [<id>...] [--all] [--strict]
workload declare <id> --kind K --runtime R --host H [--title T] [--purpose P] [--command ARGV...] [--timeout-sec N] [--force]
workload render <id> [--offline --uid U --home P]
workload provision <id> [--dry-run] [--yes] [--force] [--accept-degraded] [--enable]
workload adopt <id> [--yes] # a hand made unit: declare its placement.label_prefix
workload reconcile [<id>...] [--all] [--host H] [--no-probe] [--verbose] [--propose-inventory] [--json] [--notify]
workload view [<id>...] [--host H] [--no-probe] [--out PATH] --now STAMP [--poll-sec S]
workload publish [<id>...] [--host H] [--no-probe] --to HOST --dest DIR --now STAMP [--page-name NAME] [--attach PATH]... [--url URL] [--stale-after-min N] [--poll-sec S] [--yes]
workload retire <id> --reason TEXT [--superseded-by ID] [--keep-artifact] [--yes] [--dry-run]
What ships with it
60 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.
- .gitignore 34 B
- engine/__init__.py 0 B runs code
- engine/backends/__init__.py 2.1 KB runs code
- engine/backends/base.py 23 KB runs code
- engine/backends/cron.py 12 KB runs code
- engine/backends/dispatcher.py 7.3 KB runs code
- engine/backends/inert.py 3.3 KB runs code
- engine/backends/launchd.py 22 KB runs code
- engine/backends/systemd.py 17 KB runs code
- engine/backends/wrapper.py 20 KB runs code
- engine/cli.py 47 KB runs code
- engine/config.py 5.1 KB runs code
- engine/errors.py 7.6 KB runs code
- engine/exec.py 14 KB runs code
- engine/hosts.py 4.5 KB runs code
- engine/inventory.py 19 KB runs code
- engine/lock.py 2.4 KB runs code
- engine/model.py 85 KB runs code
- engine/notify.py 19 KB runs code
- engine/probe.py 13 KB runs code
- engine/provision.py 36 KB runs code
- engine/publish.py 26 KB runs code
- engine/recipients.py 5.8 KB runs code
- engine/reconcile.py 77 KB runs code
- engine/render.py 5.7 KB runs code
- engine/report.py 11 KB runs code
- engine/source.py 7.8 KB runs code
- engine/stamp.py 9.0 KB runs code
- engine/view.py 157 KB runs code
- references/backends.md 10 KB
- references/declare.md 17 KB
- references/provision.md 12 KB
- references/reconcile.md 8.2 KB
- run-tests.sh 212 B runs code
- scripts/tests/mutate.py 4.7 KB runs code
- scripts/tests/run.sh 2.2 KB runs code
- scripts/tests/tally.awk 3.1 KB
- tests/__init__.py 0 B runs code
- tests/conftest.py 38 KB runs code
- tests/fixtures/checks/sample.yaml 539 B
- tests/fixtures/checks/storage.yaml 328 B
- tests/fixtures/corpus/calendar-export.yaml 573 B
- tests/fixtures/corpus/chat-channel.yaml 205 B
- tests/fixtures/corpus/contract-review-reminder.yaml 501 B
- tests/fixtures/corpus/daily-health-report.yaml 874 B
- tests/fixtures/corpus/public-funnel.yaml 304 B
- tests/fixtures/corpus/voice-channel.yaml 439 B
- tests/fixtures/corpus/voicememo-notify.yaml 452 B
- tests/fixtures/derived/adopted-prefix-daemon.yaml 567 B
- tests/fixtures/derived/ambiguous-check-report.yaml 418 B
- tests/fixtures/derived/block-style-report.yaml 1.1 KB
- tests/fixtures/derived/checked-report.yaml 465 B
- tests/fixtures/derived/cron-cadence.yaml 410 B
- tests/fixtures/derived/cron-daemon-refused.yaml 205 B
- tests/fixtures/derived/early-daily-report.yaml 1.1 KB
- tests/fixtures/derived/elevated-daemon.yaml 327 B
- tests/fixtures/derived/exotic-recurrence-watched.yaml 1.0 KB
- tests/fixtures/derived/exotic-recurrence.yaml 456 B
- tests/fixtures/derived/foreign-timezone-report.yaml 431 B
- tests/fixtures/derived/linux-timer-report.yaml 553 B
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.
- 2d ago First seen · 607 lines · 248 tokens per session scan A 58311567063a
workload is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 2d ago), licensed MIT. It adds 248 tokens to every session and 9,368 once invoked, about $0.0012 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
xlsx
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify…
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
pptx
Presentation creation, editing, and analysis. When Claude needs to work with presentations (.pptx files) for: (1) Creating new presentations, (2) Modifying or editing content, (3) Working with layouts, (4) Adding comments or speaker notes, or any other presentation tasks.
docx
Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4)…
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
retrospect-external-babysitter-run
For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/ /) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but…