meeting-prep-five-minutes

meeting-prep-five-minutes is a skill for Claude Code, Codex from mardab96/b2b-lead-generation-claude-skills. It costs 62 tokens per session (967 once invoked), scanned A, original, MIT.

A short brief prepared before a sales call, covering the company, likely priorities, useful questions and possible reasons not to pursue the deal. It is designed for situations where only a few minutes are available for preparation.

In plain words
What is it for?
Use it before a first call, follow-up or late-stage sales conversation. Provide the company's name and website, the participants and roles, what you sell, and the conversation stage.
Why use it?
It reduces the chance of entering a call without knowing who the company is or what the participants may care about. It keeps preparation short enough to use between back-to-back meetings.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it before a first call, follow-up or late-stage sales conversation. Provide the company's name and website, the participants and roles, what you sell, and the conversation stage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes
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 mardab96/b2b-lead-generation-claude-skills --skill meeting-prep-five-minutes
Clone the repo
git clone --depth 1 https://github.com/mardab96/b2b-lead-generation-claude-skills

Made for: Claude Code, Codex.

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 meeting-prep-five-minutes

README.md
[![agentmods](https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes/github.svg)](https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes)
Your own site
<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes/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 meeting-prep-five-minutes

Your own site · 80×15
<a href="https://agentmods.dev/skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes"><img src="https://agentmods.dev/badge/skills/mardab96/b2b-lead-generation-claude-skills/meeting-prep-five-minutes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 967 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.00062 $0.00967
Opus 5 $0.00031 $0.00483
Sonnet 5 $0.00012 $0.00193
Haiku 4.5 $0.00006 $0.00097

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

Security

Grade A, and why

meeting-prep-five-minutes 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 12d 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.

meeting-prep-five-minutes/SKILL.md · 96 lines

How it starts

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

Meeting Prep in Five Minutes

Use this skill when

There is a call soon and nobody has read anything about the company.

You have twenty minutes before a call. The goal is to walk in knowing three things you did not know, rather than forty you will not remember.

The output is deliberately short. A brief nobody reads before the call is worth less than no brief, because it also consumed the prep time.

Required input

  • Company name and website.
  • Who is on the call, and their roles.
  • Whether this is a first call, a follow-up, or a late-stage conversation. The brief is different for each.
  • What you sell.

Useful if it exists, skipped without complaint if not:

  • previous emails or notes with this account
  • how they arrived: inbound, outbound, referral, event
  • which competitor they are likely using
  • your typical deal size and the size this one looks like

Analysis workflow

  1. Establish the basics fast: what they sell, roughly how big, who they sell to. Two minutes, not twenty.
  2. Work out who is actually in the room. A founder, a head of department and a procurement lead each want a different conversation, and preparing for the wrong one is worse than preparing for none.
  3. Find at most three specifics worth mentioning. More than three will not survive the first five minutes of an actual conversation.
  4. Write the questions you cannot answer from research. The point of the call is what the website does not say, so a brief that answers everything has prepared the wrong things.
  5. Name the likely objection for this profile, and the honest response to it.
  6. Write the disqualifiers explicitly, then decide what a good outcome is. Not "a great conversation", a specific next step.

Decision rules

  • Three facts maximum. This is a hard limit, not a guideline.
  • Questions beat statements in the brief. If the brief is mostly things to say, it is a pitch script and the call will feel like one.
  • If the research contradicts what the CRM says about this account, flag the contradiction rather than smoothing it over.
  • If this is a follow-up call, the previous conversation outranks anything found online.
  • If nothing meaningful can be found, say so and lean the brief entirely on questions. That is a normal outcome for small and private companies.

Read the full file on GitHub · 96 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. 12d ago First seen · 96 lines · 0 tokens per session scan A 9b13bddbd216

Subscribe to this mod's changes

meeting-prep-five-minutes is a skill published in the GitHub repository mardab96/b2b-lead-generation-claude-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 62 tokens to every session and 967 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens