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 bridge-greetinggit 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/bridge-greeting)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/bridge-greeting"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-greeting/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/bridge-greeting"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/bridge-greeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 79 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00125 | $0.01951 |
| Opus 5 | $0.00063 | $0.00975 |
| Sonnet 5 | $0.00025 | $0.00390 |
| Haiku 4.5 | $0.00013 | $0.00195 |
Grade A, and why
bridge-greeting 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 9d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bridge Greeting
A login-shell greeting that is instance-aware: the org folder you open the terminal in resolves to a Bridge instance, and the greeting then shows that instance's identity — logo, colours, calendar tags, task board, and repos.
Home / unknown dirs → the full system dashboard (fastfetch cascade + global board). Inside an org tree → a focused panel for the resolved instance.
The model — branding belongs to the Bridge, not the script
The greeting reads its visual identity from the resolved instance's theme
(themes/<theme>.yaml → branding: block), so a logo "comes from" its Bridge
instance the same way identity/agent/ and vocabulary do. Three layers:
| Layer | Owns | Tier |
|---|---|---|
Engine (scripts/render-motd.sh) |
discovery, rendering, board parsing — no instance literals | CORE → open-bridge |
Theme branding (themes/<theme>.yaml branding:) |
logo path, logo_color_1/2, calendar_tags per instance |
per-instance |
Local override (~/.config/fastfetch/bridge-motd.local.sh) |
per-org fallbacks for instances whose theme has no branding: yet; the org→instance machine map |
USER (machine-local, never committed) |
Discovery scans ~/Developer/*/*/bridge-config.yaml to build the
org-folder → instance map automatically — no hardcoded instance names in the engine.
Purpose tagline — the instance's north-star under the logo
When the resolved instance's bridge-config.yaml has a non-empty
purpose.statement, render it as the subtitle / tagline directly under the
logo, alongside the theme-derived identity the greeting already shows — so the
terminal opens reading as what this Bridge is for, not a bare wordmark. Empty
purpose.statement → no tagline line (today's behaviour). This is display only; the
purpose never changes what the greeting can show.
gen-logo.py — make an instance its logo
uv run --with pyfiglet python scripts/gen-logo.py --top ACME --bottom CORP > assets/logos/acme.txt
uv run --with pyfiglet python scripts/gen-logo.py --top ACME --umlaut 1 > assets/logos/acme.txt
What ships with it
5 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.
- 9d ago First seen · 150 lines · 125 tokens per session scan A 675a3dd60362
bridge-greeting is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed 2d ago), licensed MIT. It adds 125 tokens to every session and 1,951 once invoked, about $0.0006 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
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
digest
NOTE: this skill requires connected chat / email / project-tracker / docs MCPs, which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Cross-tool rollup of what's pending, what shipped, and what's blocked across chat / email / project tracker /…
agency-hospitality-guest-services
Comprehensive hospitality guest services specialist for hotels, resorts, restaurants, and event venues — covering reservations, check-in/check-out, concierge services, guest complaint resolution, loyalty program management, and post-stay follow-up to deliver exceptional guest experiences that drive loyalty and revenue.
agency-hr-onboarding
Comprehensive HR onboarding specialist for employee orientation, documentation management, compliance tracking, benefits enrollment, culture integration, and new hire support — delivering a seamless first-day-to-first-year experience that drives retention and productivity.
agency-it-service-manager
Expert IT service management specialist using ITIL 4 framework for service catalog design, incident and problem management, change control, SLA governance, CMDB maintenance, and continual service improvement — ensuring IT delivers reliable, measurable business value across any organization size.
agency-healthcare-customer-service
Empathetic healthcare customer service specialist for patient support, billing inquiries, appointment management, insurance questions, complaint resolution, and seamless escalation to clinical or administrative staff.