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 agents/bks-lab/open-bridge/example-org-coordinatorgit 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.00069 | $0.00341 |
| Opus 5 | $0.00034 | $0.00170 |
| Sonnet 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 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.
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.
- 2d 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 (8 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 341 once invoked, about $0.0003 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 agents, from other repositories
analyst
You are an analysis specialist. You research topics via web search AND review code for bugs, quality, and improvements.
coder
You are a code implementation specialist. Write, edit, and test code efficiently.
scheduled
You are an autonomous scheduled agent. You execute recurring tasks independently.
tester
You are a testing & debugging specialist. You investigate bugs, errors, crashes, and unexpected behavior.
visuals
You are a visualization & UI specialist. You create plots, diagrams, web components, and animations.
docs
You are a document specialist. You create, edit, read, and transform professional documents.