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/briefingnpx skills add bks-lab/open-bridge --skill briefinggit 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/briefing)<a href="https://agentmods.dev/skills/bks-lab/open-bridge/briefing"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/briefing.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.1 | $0.00076 | $0.01036 |
| Opus 5 | $0.00038 | $0.00518 |
| Sonnet 5 | $0.00015 | $0.00207 |
| Haiku 4.5 | $0.00008 | $0.00104 |
Grade A, and why
briefing 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 6d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Briefing
Daily and on-demand briefing. Read the referenced file ONLY when triggered.
Arguments
| Argument | Effect | Default |
|---|---|---|
(none) |
Full briefing — all 4 streams + Phase 2 board.md sync | — |
--quick |
Focus box + Stream A only; skips trackers, companion data, channels, Phase 2 | false |
--skip-trackers |
All streams except Stream B (offline-friendly); Phase 2 still runs | false |
--commits YYYY-MM-DD |
Detailed commit analysis for one day (sessions, time est., types) — see references/commit-analysis.md |
— |
--html |
After terminal output, delegate to /bridge-dashboard to render the operational HTML dashboard |
false |
Mode × Phase matrix
| Phase | default | --quick |
--skip-trackers |
|---|---|---|---|
| Phase 0 (smart detection + day block) | ✅ | ✅ | ✅ |
| Stream A (local state) | ✅ | ✅ | ✅ |
| Stream B (trackers fan-out) | ✅ | ❌ | ❌ |
| Stream C (companion: calendar, imports) | ✅ | ❌ | ✅ |
| Stream D (channels) | ✅ | ❌ | ✅ |
| Phase 2 (board.md sync) | ✅ | ❌ | ✅ |
| Phase 3 (log entry) | ✅ | ✅ | ✅ |
| Phase 4 (terminal output) | ✅ | ✅ | ✅ |
Prerequisites
bridge-config.yamlwithwork.enabled: true. If not: offer setup.- Standing orders are loaded at session start (per CLAUDE.md). If
/briefingis invoked standalone (e.g. via cron or a long-running session), manually loadprotocols/standing-orders/*.mdandprotocols/standing-orders/user/*.mdbefore Phase 1 — theapplicationssurface logic in Stream C depends on them, and an applications order is user-tier (a*.mdglob alone does not reachuser/).
Decision Tree
User wants to...
├── Full daily briefing → Read references/workflow.md
├── Quick local-only briefing → Read references/workflow.md (--quick path)
├── Detailed commit analysis → Read references/commit-analysis.md
├── Are we behind on anything? → Read references/upstream-summary.md
│ (covers BOTH inbound channels: CORE from
│ the `role: oss-core` upstream, and every
│ subscribed org overlay. Needs an
│ `upstreams:` list in bridge-config.yaml;
│ a Bridge with none skips)
└── Questions about briefing → Answer from this file
What ships with it
3 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.
- 6d ago First seen · 97 lines · 76 tokens per session scan A 0e21da003d84
briefing is a skill published in the GitHub repository bks-lab/open-bridge (8 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 1,036 once invoked, about $0.0004 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
kungfu-agent-onboarding
Use when a user asks to understand, start, inspect, extend, or safely operate installed Kungfu; verify the installed pack, select one intent route, personalize the explanation, and propose one smallest safe next action.
cog-braindump-capture
Capture raw thoughts with automatic domain classification and vault routing.
context-preservation
State capture and restore across context window compactions. Monitors usage thresholds and serializes quality, task, and spec state for seamless continuation.
cog-knowledge-consolidation
Build structured knowledge frameworks from scattered vault notes with source attribution.
cog-onboarding
Personalize COG Second Brain workflow through role pack selection and vault initialization.
cog-weekly-reflection
Cross-domain pattern analysis with personal, professional, and project domain synthesis.