preparing-for-a-meeting

preparing-for-a-meeting is a skill for Claude Code from redhuntlabs/wizard. It costs 32 tokens per session (884 once invoked), scanned A, original, MIT.

A short preparation brief for a work meeting, covering key facts, points to mention, and questions to ask. It can use recent context and note sources for facts.

In plain words
What is it for?
Use it before one-to-ones, customer calls, interviews, reviews, introductions, and decision meetings.
Why use it?
It helps you enter a meeting aware of the important background instead of spending the first minutes reconstructing it.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the wizard plugin — 37 skills, 6 commands, 1 agent, 1 hook shipped together

Good fit Use it before one-to-ones, customer calls, interviews, reviews, introductions, and decision meetings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/redhuntlabs/wizard/preparing-for-a-meeting
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.

Any agent
npx skills add redhuntlabs/wizard --skill preparing-for-a-meeting
Clone the repo
git clone --depth 1 https://github.com/redhuntlabs/wizard

Made for: Claude Code.

Or install wizard, the plugin that ships this one along with the rest of its 37 skills, 6 commands, 1 agent, 1 hook.

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 preparing-for-a-meeting

README.md
[![agentmods](https://agentmods.dev/badge/skills/redhuntlabs/wizard/preparing-for-a-meeting/github.svg)](https://agentmods.dev/skills/redhuntlabs/wizard/preparing-for-a-meeting)
Your own site
<a href="https://agentmods.dev/skills/redhuntlabs/wizard/preparing-for-a-meeting"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/preparing-for-a-meeting/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 preparing-for-a-meeting

Your own site · 80×15
<a href="https://agentmods.dev/skills/redhuntlabs/wizard/preparing-for-a-meeting"><img src="https://agentmods.dev/badge/skills/redhuntlabs/wizard/preparing-for-a-meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 884 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.00032 $0.00884
Opus 5 $0.00016 $0.00442
Sonnet 5 $0.00006 $0.00177
Haiku 4.5 $0.00003 $0.00088

Measured 9d ago against content hash e37b25d43ad4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

preparing-for-a-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 9d 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.

spells/work/preparing-for-a-meeting/SKILL.md · 109 lines

How it starts

The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Preparing for a Meeting

What this does

Generates a 60-second-readable brief you scan before the meeting starts. Three things you must know, two things to mention, three questions you could ask.

When to use

  • Any meeting where you need to walk in able to talk substance
  • 1:1s where you want to follow up on prior threads
  • Customer calls where the client's recent context matters
  • Interviews (yours or theirs)

What you bring (Inputs)

  • Meeting topic or attendees
  • Meeting purpose (intro / sale / interview / review / decision / other)
  • Time available to prep (5-30 min)

What you get (Output)

A one-screen brief with: TLDR, Key facts, Things to mention, Questions to ask.

How it works (Steps)

This is a simple workflow.

Stages

Stage 1: Identify the must-know facts

Three things you'd be embarrassed not to know in this meeting. Examples: their company's recent news, their last interaction with you, the current state of the project being discussed.

Stage 2: Find each fact (with source)

For each must-know, find the answer and note the source so you could verify mid-meeting if asked.

Stage 3: Pick 2 things to mention

Specific things from prior interactions or recent context that the other party would notice and appreciate. Avoids generic "great chat last time" filler.

Stage 4: Generate 3 questions

Open-ended questions you could ask. Specific to the context, not generic ("what are your priorities?").

Stage 5: Format

TLDR (1 sentence) / Key facts (3 bullets with sources) / Things to mention (2 bullets) / Questions to ask (3 bullets).

Checkpoints

  • After Stage 1: 3 must-knows identified
  • After Stage 2: every must-know has an answer with a source
  • After Stage 3: things-to-mention reference recent / specific / non-obvious info
  • After Stage 4: questions are open-ended and specific
  • After Stage 5: brief fits on one screen

Loop-back conditions

Return to Stage 1 if research reveals a must-know you missed.

Read the full file on GitHub · 109 lines

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. 9d ago First seen · 109 lines · 32 tokens per session scan A e37b25d43ad4

Subscribe to this mod's changes

preparing-for-a-meeting is a skill published in the GitHub repository redhuntlabs/wizard (9 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 884 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.