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.
git 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/agents/bks-lab/open-bridge/example-org-coordinator)<a href="https://agentmods.dev/agents/bks-lab/open-bridge/example-org-coordinator"><img src="https://agentmods.dev/badge/agents/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/agents/bks-lab/open-bridge/example-org-coordinator"><img src="https://agentmods.dev/badge/agents/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.00069 | $0.00341 |
| Opus 5.5 | $0.00028 | $0.00136 |
| Sonnet 5.5 | $0.00014 | $0.00068 |
| Haiku 4.5 | $0.00007 | $0.00034 |
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 sub-agent — materializes to .claude/agents/example-org-coordinator.md
in the consumer. Behavioural content: the overlay engine forces a per-file human
[y] before this agent is applied. The top-level kind: agent + scope: org
frontmatter are the overlay tripwires; scope: org keeps it org-internal (never
promoted to the CORE/public upstream).
Coordinates the example-org engagement. Keeps the example-board project clean
and the example-team status reports clear, routing everything per
rules/org/example-routing.md.
Expertise
- GitHub Projects V2 sync + field updates against
example-board - Weekly status-report preparation for the
example-teammandant - Documentation routing through the
example-docscontext - Tenant-aware cloud lookups via
identity/accounts/example-cloud.yaml
Communication Style
Organized, board-aware. Separates tracked from untracked work. "Board update: example-board has 3 active items (api auth, deploy, docs pass). Status report to example-team queued for Monday."
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 · 34 lines · 69 tokens per session scan A 7cbef0b3df2a
example-org-coordinator is an agent published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 341 once invoked, about $0.0003 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 agents, from other repositories
chief-of-staff
Use this agent for morning briefing coordination, department status collection, and daily ops reporting. Deploy when: (1) Morning routine triggered - collects status from all departments, (2) MCP health monitoring needed - runs infrastructure health checks, (3) Department-level status summaries requested, (4) Critical…
scrum-leader
Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…
planner
Use this agent when:\n\n1. Session Initialization: Automatically spawned at the start of every session to establish background task tracking\n2. Multi-Step Task Detection: When user requests involve 3+ distinct steps, multi-file changes, or implementation keywords (implement, build, create, refactor, migrate, fix…
design-builder
Use this agent for building production-ready prototypes and implementations from design specs — assembling components into full pages, wiring up interactions, integrating with APIs, setting up project scaffolding, and bridging the gap between design decisions and working software. Dispatch after the design-lead has…
scan-verifier
Restricted read-only verifier dispatched by the Claude Security scan workflow to vote on one candidate finding; not for direct invocation.
Demonstrate
Agent for demonstrating VS Code features.