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 makenotion/notion-cookbook --skill meeting-intelligencegit clone --depth 1 https://github.com/makenotion/notion-cookbookWrote 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/makenotion/notion-cookbook/meeting-intelligence)<a href="https://agentmods.dev/skills/makenotion/notion-cookbook/meeting-intelligence"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/meeting-intelligence/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/makenotion/notion-cookbook/meeting-intelligence"><img src="https://agentmods.dev/badge/skills/makenotion/notion-cookbook/meeting-intelligence.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00055 | $0.01051 |
| Opus 5.5 | $0.00022 | $0.00420 |
| Sonnet 5.5 | $0.00011 | $0.00210 |
| Haiku 4.5 | $0.00006 | $0.00105 |
Grade A, and why
notion-meeting-intelligence 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 21d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- notion-meeting-intelligence — 100% identical, 351 lines differ
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting intelligence
Prepare materials that help participants reach the meeting's intended outcome. Support both a concise agenda and a detailed internal pre-read without requiring both for every meeting.
Workflow
- Establish scope. Use known purpose, date, duration, attendees, audience, and project. Ask only for details that materially affect preparation. Honor requests for an agenda, pre-read, both, or a chat brief. For unspecified preparation, start with an agenda; add a separate pre-read when substantial background or internal-only strategy makes it useful. Do not invent meeting details.
- Gather relevant evidence. Fetch supplied pages directly. Otherwise search for the project or meeting, then fetch the most relevant matches. For recurring meetings, carry forward unresolved decisions and actions from previous notes. Retrieve task data or metrics only when needed; reuse sources already read. Expand retrieval to fill material gaps, not to meet a source-count target.
- Develop the brief. Extract status, changes, decisions, blockers, and open questions with source links. Distinguish source facts from your analysis and suggested frameworks. Research current company, competitor, or industry facts with available search tools when relevant; cite evidence. If research is unavailable, state the gap instead of presenting model knowledge as current research. Do not add generic industry context just to fill a section.
- Prepare the requested materials. Use the structures below or load one matching template. Scale depth to the meeting's importance and available time. Keep the agenda's time allocations within the known duration. Show unknown owners, dates, and metrics as unknown rather than guessing.
- Deliver or save. Treat draft status separately from destination: save a draft in Notion when requested, using the database's draft status if applicable. Keep chat-only or explicitly unsaved drafts in chat. For Notion output, use the supplied destination or an established meeting location; resolve material ambiguity before writing. Fetch a database schema once if needed. Update an existing meeting document when appropriate. Check write results and return links, noting incomplete work; read back an update if its result is unclear.
What ships with it
22 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.
- evaluations/agenda-only.json 710 B
- evaluations/current-external-context.json 1.2 KB
- evaluations/decision-meeting-prep.json 1.4 KB
- evaluations/discover-meeting-context.json 2.9 KB
- evaluations/linked-actions.json 2.6 KB
- evaluations/partial-action-recovery.json 2.4 KB
- evaluations/post-meeting-update.json 850 B
- evaluations/README.md 2.8 KB
- evaluations/save-draft.json 1.0 KB
- evaluations/status-meeting-prep.json 1.8 KB
- examples/customer-meeting.md 5.2 KB
- examples/executive-review.md 2.1 KB
- examples/project-decision.md 13 KB
- examples/sprint-planning.md 2.1 KB
- reference/brainstorming-template.md 1.5 KB
- reference/decision-meeting-template.md 1.8 KB
- reference/meeting-to-actions.md 2.6 KB
- reference/one-on-one-template.md 940 B
- reference/retrospective-template.md 941 B
- reference/sprint-planning-template.md 1.3 KB
- reference/status-update-template.md 1.3 KB
- reference/template-selection-guide.md 2.4 KB
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.
- 21d ago Changed · -209 lines · +5 tokens per session 94632e5dc569
- 1mo ago First seen · 298 lines · 50 tokens per session scan A 8abefc02d5e2
notion-meeting-intelligence is a skill published in the GitHub repository makenotion/notion-cookbook (220 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,051 once invoked, about $0.0002 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…