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/workspacenpx skills add bks-lab/open-bridge --skill workspacegit 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/workspace)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/workspace"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/workspace.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00190 | $0.01885 |
| Opus 5 | $0.00095 | $0.00942 |
| Sonnet 5 | $0.00038 | $0.00377 |
| Haiku 4.5 | $0.00019 | $0.00188 |
Grade A, and why
workspace 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace — bind repos + config into one named project container
A workspace is a named project identity that pulls together the code repos and config overlays you work on as one unit. It has two disjoint halves:
- Identity (which project is this) — name, member roots, git remotes —
lives in the machine-global shared registry
~/.workspaces/workspaces.json, a tool-neutral file any conformant tool can read/write under a documented lock + atomic-replace protocol. This is how a workspace means the same thing across tools on the machine. - Materialization (how does THIS repo realise it) — the actual clones, the resolved-SHA lockfile, the fork-safety exclude block — is repo-local and never leaves the repo.
The engine is scripts/workspace.py (standalone, stdlib-only) — a shared
repo-root utility shipped with the Bridge repo itself, not a file inside this
skill's own directory. This skill is the /workspace surface over it. Run
the referenced file ONLY when the decision tree sends you there.
/workspace is the umbrella; for the deep org-overlay subscription flow
(manifest validation, per-file plan, 3-way merge, sync/diff) it delegates to and
cross-references /overlay (the bridge-overlay skill). Binding a config
overlay via workspace subscribe … --role config calls that same engine
(overlay.py) under the hood.
When to use
- "Make a workspace for project X" →
create - "Add this repo to the workspace" / "bind these repos together" →
subscribe … --role code - "Pull the org's shared config into this workspace" →
subscribe … --role config(delegates to/overlay) - "What workspaces do I have / are the members drifted?" →
list/status - "Drop a repo / overlay from the workspace" →
unsubscribe
NOT for:
- Managing an org overlay subscription on its own (manifest, sync, diff, authoring) →
/overlay(bridge-overlay) - Pushing YOUR changes upstream →
/promote,/bridge-sync - A knowledge-base index over a folder → a provider skill, if your instance ships one (unrelated to this "workspace")
What ships with it
2 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.
- 4d ago First seen · 138 lines · 190 tokens per session scan A 6d3cd24aeb63
workspace is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 4d ago), licensed MIT. It adds 190 tokens to every session and 1,885 once invoked, about $0.0010 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
swarm-flow
The SDLC router — figures out where a project stands and runs the right phase. Use at the START of any work in a SwarmVault project: continuing/resuming a project, starting a new one, "what's next", or before writing any feature code, spec, design, or ticket. Also use when unsure which phase (requirements, design…
swarm-init
Start a new project connected to the SwarmVault — register it, wire platform adapters, offer git init, set vault-as-default. Use when starting a new project, connecting a project to the vault, or when the user asks to set up SwarmVault in a directory.
swarm-implement
Implementation phase — turn a validated design into dependency-ordered tickets, then work them as one of N parallel agents with atomic claims, model tiering, and tests-in-ticket definition of done. Use to plan tickets from a design, pick up/continue implementation work, coordinate parallel agents, or check what to…
swarm-migrate
Bring existing projects into the SwarmVault — register, mirror docs, optionally mine the repo into SDLC artifacts and resume the flow mid-phase (brownfield adoption). Use when the user wants existing projects migrated/connected to the vault, or an existing codebase placed into the SDLC flow.
swarm-eject
Disconnect a project from SwarmVault and choose what happens to its knowledge — keep it, export it into the repo, or delete it. Use when the user wants to stop using SwarmVault here, remove the vault wiring, uninstall the framework from a project, offboard or archive a project, or delete a project's vault data.
task-tracker
Управление задачами: добавить, завершить, показать список, приоритеты. Triggers: 'задача', 'задачи', 'todo', 'добавь задачу', 'что сделать', 'список дел', 'task'.