debrief

debrief is a skill for Claude Code, Codex from bks-lab/open-bridge. It costs 81 tokens per session (2,454 once invoked), scanned A, original, MIT.

A workflow for processing meeting transcripts—written or recorded meeting text—to classify the meeting, correct names, extract insights, and propose tasks.

In plain words
What is it for?
It can run a full or quick workflow, classify transcripts, apply name corrections, process batches by date, and reconcile tasks with GitHub.
Why use it?
It turns an unstructured transcript into organized notes and follow-up work while supporting different levels of processing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It can run a full or quick workflow, classify transcripts, apply name corrections, process batches by date, and reconcile tasks with GitHub.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/bks-lab/open-bridge/debrief
Install

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.

Any agent
npx skills add bks-lab/open-bridge --skill debrief
Clone the repo
git clone --depth 1 https://github.com/bks-lab/open-bridge

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for debrief

README.md
[![agentmods](https://agentmods.dev/badge/skills/bks-lab/open-bridge/debrief/github.svg)](https://agentmods.dev/skills/bks-lab/open-bridge/debrief)
Your own site
<a href="https://agentmods.dev/skills/bks-lab/open-bridge/debrief"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/debrief/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.

agentmods 80×15 button for debrief

Your own site · 80×15
<a href="https://agentmods.dev/skills/bks-lab/open-bridge/debrief"><img src="https://agentmods.dev/badge/skills/bks-lab/open-bridge/debrief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,454 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00081 $0.02454
Opus 5.5 $0.00032 $0.00982
Sonnet 5.5 $0.00016 $0.00491
Haiku 4.5 $0.00008 $0.00245

Measured 4d ago against content hash d1c8a1a6fd37, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

debrief 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 4d 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.

skills/debrief/SKILL.md · 196 lines

How it starts

The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Debrief

Process a meeting transcript. Read the referenced file ONLY when triggered.

Sources and flow variants

Sources scanned: legacy work.imports_dir plus doc_sensor.scan_paths entries with kind: recordings (catches PARA tree 2_AREAS/Import_Audio/ after the PARA migration). Already-archived basenames in work/archive/days/ are skipped as redundant.

Flow variants:

  • Full 8-phase flow (references/full-workflow.md) with GitHub task-reconciliation (references/task-reconciliation.md) and optional distribution email (references/distribution-email.md) to meeting participants.
  • Quick 5-phase flow (references/quick-workflow.md).
  • Batch flags: --all processes every unprocessed transcript in imports/; --date YYYY-MM-DD processes only that day. (Both formerly lived in /process-meeting, now merged here.)

Decision Tree

User wants to...
├── Full processing (8 phases)              → Read references/full-workflow.md
├── Quick processing (5 phases)             → Read references/quick-workflow.md
├── Classify a transcript only              → Read references/classification.md
├── Apply name corrections                  → Read references/classification.md (§ Name Corrections)
├── Generate a protocol from notes          → Read references/protocol-templates.md
├── Match actions to existing issues        → Read references/task-reconciliation.md
│                                             (called from Phase 5)
├── Pull calendar/chat context for transcript → Read references/full-workflow.md § Phase 1.5
│                                             (driven by integrations.meeting_context.*)
├── Send meeting summary email              → Read references/distribution-email.md
│                                             (called from Phase 7, after updates + protocol)
└── Questions about debrief                 → Answer from this file

Phase order (hard rule)

  1. Find → 1.5. Context Lookup (only if any integrations.meeting_context.* block in bridge-config.yaml is enabled with consumers: [debrief]) → 2. Classify + corrections → 3. Extract →
  2. (n/a — merged into 3) → 5. Task Reconciliation + Execute → 6. Protocol → 7. Distribution Email → 8. Work-log + Archive

Read the full file on GitHub · 196 lines

Files

What ships with it

6 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.

Changes

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.

  1. 4d ago Changed · +60 lines d1c8a1a6fd37
  2. 1mo ago Changed · +6 lines · -61 tokens per session 859fbee7b07a
  3. 1mo ago First seen · 130 lines · 142 tokens per session scan A c4907f8b261e

Subscribe to this mod's changes

debrief is a skill published in the GitHub repository bks-lab/open-bridge (13 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 2,454 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.

Related

Other skills, from other repositories

paperclip

Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.

paperclipai/paperclip · 54 tokens

paperclip

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

paperclipai/paperclip · 43 tokens

paperclip-board

Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.

paperclipai/paperclip · 47 tokens

paperclip-distill

Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.

paperclipai/paperclip · 54 tokens

summarize-status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

paperclipai/paperclip · 0 tokens

paperclip-task-bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

paperclipai/paperclip · 27 tokens