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 skills add chrisblattman/claudeblattman --skill pre-meeting-briefgit clone --depth 1 https://github.com/chrisblattman/claudeblattmanWrote 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/chrisblattman/claudeblattman/pre-meeting-brief)<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/pre-meeting-brief"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/pre-meeting-brief/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.
<a href="https://agentmods.dev/skills/chrisblattman/claudeblattman/pre-meeting-brief"><img src="https://agentmods.dev/badge/skills/chrisblattman/claudeblattman/pre-meeting-brief.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.05957 |
| Opus 5.5 | $0.00009 | $0.02383 |
| Sonnet 5.5 | $0.00005 | $0.01191 |
| Haiku 4.5 | $0.00002 | $0.00596 |
Grade A, and why
pre-meeting-brief 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 today.
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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Meeting Brief
v1.3 — Granola health-check simplified after the Granola public-API rewrite. Phase 0f no longer probes transcript content (the upcoming meeting has no transcript yet, and probing an arbitrary prior transcript adds latency without a clean health signal — it was producing false HOLLOW). HOLLOW classification removed for Granola entirely; Granola is now OK / DEGRADED / UNAVAILABLE only. Phase 1c fallback clarified to hunt PRIOR project meetings for context, not the upcoming one. Source-confidence table, circuit breaker, and error-handling table aligned. v1.2 — Generates a structured pre-meeting briefing from project communications. Run from a project directory.
Pulls context from WhatsApp, Gmail, Granola, Google Docs, and local files. Surfaces decisions required, open loops, and preparation needs. Optionally emails the brief to attendees.
Prerequisites
Required:
- Gmail MCP — for searching and reading message context
- Google Calendar MCP — for identifying the target meeting and attendees
Recommended:
- Granola MCP — for pulling meeting transcripts
- WhatsApp MCP — for picking up project group threads
- A project
.claude/CLAUDE.mdwith team roster, group JIDs, dashboard doc ID, and folder paths
Optional:
- A send-email helper script if you want one-step send (otherwise the skill creates a Gmail draft)
First-Time Setup
- Create a project config at
[project-root]/.claude/CLAUDE.mdwith at minimum:# Project Name ## Team - [Name] <[email protected]> — PI - [Name] <[email protected]> — Research Manager - [Name] <[email protected]> — RA ## Folders - transcripts: `transcripts/` - weekly_reviews: `weekly-reviews/` ## Config ```yaml project_keywords: [keyword1, keyword2] exclude_keywords: [unrelated_term] whatsapp_groups: ["Project Group Name"] google_doc_id: "YOUR_DOC_ID" granola_folder: "Project Folder Name" # optional
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.
- today First seen · 417 lines · 23 tokens per session scan A 7a8a29aa0286
pre-meeting-brief is a skill published in the GitHub repository chrisblattman/claudeblattman (476 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 5,957 once invoked, about $0.0001 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-11-06.
pre-meeting-brief compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| pre-meeting-briefchrisblattman/claudeblattman | Skill | 476 | yesterday | MIT | A | 23 | Claude Code |
| skill-builderyusufkaraaslan/Skill_Seekers | Skill | 15k | 1mo ago | MIT | A | 38 | Claude Code, Codex |
| strategic-revisionflonat/flonat-research | Skill | 149 | 3d ago | MIT | A | 66 | Claude Code |
| skill-creatorflonat/flonat-research | Skill | 149 | 3d ago | MIT | A | 41 | Claude Code |
| beamer-deckflonat/flonat-research | Skill | 149 | 3d ago | MIT | A | 63 | Claude Code |
| numerical-checkflonat/flonat-research | Skill | 149 | 3d ago | MIT | A | 65 | Claude Code |
| skill-preflightflonat/flonat-research | Skill | 149 | 3d ago | MIT | A | 34 | Claude Code |