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/example-org-coordinatornpx skills add bks-lab/open-bridge --skill example-org-coordinatorgit 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/example-org-coordinator)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/example-org-coordinator"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/example-org-coordinator.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.00096 | $0.00485 |
| Opus 5 | $0.00048 | $0.00243 |
| Sonnet 5 | $0.00019 | $0.00097 |
| Haiku 4.5 | $0.00010 | $0.00049 |
Grade A, and why
example-org-coordinator 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 3d 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.
What it actually says
Example-Org Coordinator
Org-overlay skill — materializes to skills/example-org-coordinator/SKILL.md
in the consumer. Behavioural content: the overlay engine forces a per-file human
[y] before this skill is applied. The top-level kind: skill tag and
metadata.scope: org are the overlay tripwires; metadata.scope: org keeps it
org-internal (never promoted to the CORE/public upstream) and is what
scripts/validate-skill-scope.py reads.
What it does
Coordinates every example-org operation behind one trigger so the main session
never reaches for raw gh or az commands:
- Board — reads field values + state mappings from
workflow/projects/example-board.yaml, then drives the board throughgithub-projects-manager(issue creation, field transitions, board queries). - Status reports — collects board state into a weekly update for the
example-teammandant (identity/mandants/example-team.yaml). - Docs — routes documentation through the
example-docscontext (workflow/contexts/example-docs.yaml) and itssync.defaults. - Cloud — resolves tenant ID + token URI from
identity/accounts/example-cloud.yamlbefore any cloud op; never hardcodes.
Conventions
- Never set a board item to "Done" directly — "In Review" first, human confirms.
- Always use the exact Status option strings declared in the project config.
- Follow
rules/org/example-routing.md; on conflict with a CORE rule, the CORE rule wins.
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.
- 3d ago First seen · 47 lines · 96 tokens per session scan A 72005cc5787c
example-org-coordinator is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 485 once invoked, about $0.0005 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…
operating-coordharness
Operates a local CoordHarness board for multi-agent work, bounded context retrieval, typed handoffs, and tracked CPU or GPU jobs. Use when an agent needs to orient, claim, renew, complete, pause, hand off, retrieve context, or attach a long-running process without creating a second source of truth.
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.