catch-up

A command that moves captured notes and meeting transcripts into a business knowledge store, while recording whether each item has been processed. It also checks names against a stored glossary.

In plain words
What is it for?
Use it to process files in the capture inbox, pasted notes, and connected meeting transcripts, then offer the next step for distilling them.
Why use it?
It reduces the manual work of emptying an inbox of notes and helps keep names consistent before information is used elsewhere.

Command for Claude Code

Part of the founder-os plugin — 9 skills, 45 commands, 6 hooks shipped together

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.

agentmods
npx agentmods add commands/arcassystems/founderos/catch-up
Clone the repo
git clone --depth 1 https://github.com/ARCASSystems/FounderOS

Made for: Claude Code.

Or install founder-os, the plugin that ships this one along with the rest of its 9 skills, 45 commands, 6 hooks.

Per session 74 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 186 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00074 $0.00186
Opus 5 $0.00037 $0.00093
Sonnet 5 $0.00015 $0.00037
Haiku 4.5 $0.00007 $0.00019

Measured 2d ago against content hash 93820d0ff6d9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

catch-up 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.

.claude/commands/catch-up.md · 10 lines

What it actually says

Catch up

Run the catch-up skill (skills/catch-up/SKILL.md) exactly as written: sweep capture/inbox/, any pasted text, and a connected meeting-notes tool into brain/rants/ with processed: false, apply the name pass against context/names.md, move swept files to capture/inbox/.processed/, report one line per capture, and offer /dream.

If $ARGUMENTS contains pasted text, treat it as the capture to file.

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. 2d ago First seen · 10 lines · 74 tokens per session scan A 93820d0ff6d9

Subscribe to this mod's changes

catch-up is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 19d ago), licensed MIT. It adds 74 tokens to every session and 186 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.