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 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/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/example-org-coordinator"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/example-org-coordinator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00096 | $0.00485 |
| Opus 5.5 | $0.00038 | $0.00194 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (13 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 485 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
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.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
pr-shepherding
Monitor PR lifecycle from creation through merge including CI monitoring, review comment handling, thread resolution, and merge readiness verification.
team-pr
Use for opening PRs only on explicit request. Never infer from passed verification. Includes project terms, evidence, and risk.