Borrowing it
Nothing to install: this file belongs to ARCASSystems/FounderOS. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ARCASSystems/FounderOS/main/.claude/commands/pre-meeting.mdgit clone --depth 1 https://github.com/ARCASSystems/FounderOSWrote 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/commands/arcassystems/founderos/pre-meeting)<a href="https://agentmods.dev/commands/arcassystems/founderos/pre-meeting"><img src="https://agentmods.dev/badge/commands/arcassystems/founderos/pre-meeting.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.00039 | $0.00811 |
| Opus 5 | $0.00019 | $0.00405 |
| Sonnet 5 | $0.00008 | $0.00162 |
| Haiku 4.5 | $0.00004 | $0.00081 |
Grade A, and why
pre-meeting 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-meeting gate
You are enforcing a hard gate. Meetings leak value when no capture artifact and no ask are declared up front. This command blocks the meeting from starting until both are named.
The argument passed is the person or meeting name: $ARGUMENTS.
Procedure (mandatory, in order)
-
If
$ARGUMENTSis empty, reply exactly:Who is the meeting with? Re-run as /pre-meeting <person>.and stop. -
Ask the founder these two questions as a single message, numbered, nothing else:
Gate before this meeting. Two answers required. 1. Capture artifact - what tangible thing leaves this meeting? (transcript, signed NDA, logged row in clients.md, proposal sent, scoped brief, specific decision recorded) 2. Ask - what are you asking them for? (intro, signature, commitment, referral, paid engagement, answer to a specific question) No vague answers. "Stay in touch" and "see where it goes" are not artifacts or asks. -
Wait for the reply. Parse the two answers.
-
If either answer is missing, empty, or falls into the vague-answer list ("stay in touch", "see where it goes", "build rapport", "catch up", "keep warm", "get to know them"), refuse. Reply:
Rejected. That is not an artifact / that is not an ask. Re-answer both questions. Binary: answer or cancel the meeting.Then re-present the two questions. Loop until both answers are concrete. Do not proceed otherwise.
-
Once both answers are concrete, apply the private-tag filter then write: scan the answers for
<private>...</private>blocks (case-insensitive). Remove every matched block (including the tags) from the text before writing. If the entire input is wrapped in<private>, write nothing and report "skipped - content was tagged private." Then append this exact block tobrain/log.md(use the Edit or Write tool - read the file first, then append at the end). Use the current real date and time. Ifbrain/log.mddoes not exist, create it.
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 · 63 lines · 39 tokens per session scan A 5e54ad514746
pre-meeting is a command published in the GitHub repository ARCASSystems/FounderOS (5 stars, last pushed 22d ago), licensed MIT. It adds 39 tokens to every session and 811 once invoked, about $0.0002 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 commands, from other repositories
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
review
Comprehensive code review for blz changes.
cheatsheet
Generate a one-page exam cheatsheet from course-index and errors/log.md. Outputs to cheatsheet/final.md. Optionally convert to PDF.
index-cmd
The index command reindexes a repository and synchronizes its anchor ledger while selecting human-readable, JSON, or quiet output.
doc-review
Review documentation for quality, accuracy, and completeness.