personal-os: Command for Claude Code

.claude/commands/debrief.md

debrief is a command for Claude Code from jordantcarlisle/personal-os. It costs 0 tokens per session (256 once invoked), scanned A, original, MIT.

A meeting-debrief command that turns a meeting or event into recorded action items, decisions, people notes, project updates, and follow-ups.

In plain words
What is it for?
Capturing who owns each task, recording decisions, updating project files, noting important details about attendees, and adding reminders or waiting items.
Why use it?
It prevents useful outcomes from being lost after a meeting and makes ownership and deadlines explicit.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is jordantcarlisle/personal-os's own configuration. It tells Claude Code how to work on personal-os itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything personal-os configures →

Reuse

Borrowing it

Nothing to install: this file belongs to jordantcarlisle/personal-os. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/jordantcarlisle/personal-os/main/.claude/commands/debrief.md
Clone the repo
git clone --depth 1 https://github.com/jordantcarlisle/personal-os

Made for: Claude Code.

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/commands/jordantcarlisle/personal-os/debrief/github.svg)](https://agentmods.dev/commands/jordantcarlisle/personal-os/debrief)
Your own site
<a href="https://agentmods.dev/commands/jordantcarlisle/personal-os/debrief"><img src="https://agentmods.dev/badge/commands/jordantcarlisle/personal-os/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/commands/jordantcarlisle/personal-os/debrief"><img src="https://agentmods.dev/badge/commands/jordantcarlisle/personal-os/debrief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 256 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.
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.00000 $0.00256
Opus 5 $0.00000 $0.00128
Sonnet 5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00026

Measured 10d ago against content hash 6083c9cfd712, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, 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 10d 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.

.claude/commands/debrief.md · 27 lines

What it actually says

Chief of Staff — Meeting Debrief

Extract maximum value from a meeting or event.

Process

  1. Context: Ask "What was the meeting about? Who was there?"

  2. Action Items: Ask "What action items came out of this?" For each item:

    • Who owns it? What's the deadline?
    • Your items → add to 00-cockpit/inbox.md or directly to dashboard
    • Others' items → add to Waiting For table on dashboard with person and date
  3. Decisions: Ask "Were any decisions made worth logging?" If yes: create entry in 03-resources/knowledge/decisions/ using the template, or delegate to Memory Keeper agent.

  4. People Notes: Ask "Anything notable about anyone in the meeting?"

    • Communication style, priorities, concerns they expressed
    • If Relationship Manager module is active, update contact profiles
  5. Project Updates: Ask "Does this affect any active projects?" If yes: update the relevant project file in 01-projects/

  6. Follow-ups: Ask "Any follow-ups that weren't captured as action items?" If yes: schedule or add to inbox

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. 10d ago First seen · 27 lines · 0 tokens per session scan A 6083c9cfd712

Subscribe to this mod's changes

debrief is a command published in the GitHub repository jordantcarlisle/personal-os (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 256 tokens. 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.