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 swan-gtm/gtm-skills --skill meeting-prepgit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/meeting-prep)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/meeting-prep"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/meeting-prep/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/swan-gtm/gtm-skills/meeting-prep"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/meeting-prep.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.00161 | $0.01763 |
| Opus 5 | $0.00081 | $0.00881 |
| Sonnet 5 | $0.00032 | $0.00353 |
| Haiku 4.5 | $0.00016 | $0.00176 |
Grade C, and why
meeting-prep scanned grade C with 1 finding 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.
Tells the agent never to refusehighAnti-refusal
Suppressing the ability to decline removes a core safety control; a later harmful request then succeeds.
- Person file updated **within 24 hours** → offer to reuse it: "I have a fresh profile on this person — use it, or refresh?" (Meeting prep is per-meeting, not per-day — never refuse a second prep in one day.) How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting prep
Runs before any meeting where you'd benefit from knowing the people across the table better than they expect. Produces one briefing per meeting: who the attendees are, what they've been saying publicly, how they connect to each other, what's happening at their company, and exactly what to bring up — never a generic dossier.
The play
1. Pin down the meeting
Extract from the request (or ask): attendee names, company, meeting date, and any context the user volunteers ("they're evaluating us", "board intro"). If a calendar is connected, offer to pull today's meetings so the user can pick one; if not, skip silently. If only a name is given, proceed and infer the company from research.
Then establish the meeting type, because it gates the whole briefing shape:
| Signal in the request | Type |
|---|---|
| "prospect", "demo", "sales call" | Sales / discovery |
| "interview", "candidate" | Interview |
| "board", "investor" | Board / investor |
| "partner", "integration" | Partnership |
| "check-in", "sync", "1:1" with a colleague | Internal |
| No signal | Ask — don't guess |
The type decides whether the Value Positioning section is produced: yes for sales/discovery, partnership, and board/investor; no for interview, internal, and general external. That's worth one clarifying question when there's no signal.
2. Load what you already know
Keep a running file per person and per company in your workspace (e.g. people/alex-kim.md, companies/widgetco.md). Before searching:
- Person file updated within 24 hours → offer to reuse it: "I have a fresh profile on this person — use it, or refresh?" (Meeting prep is per-meeting, not per-day — never refuse a second prep in one day.)
- Person file under 30 days old → load it as known context and research only what's new since. Pass the known facts into the research so it doesn't re-report them.
- Over 30 days old or missing → full refresh.
Follow cross-references between files: if an attendee's file links to a company or competitor you've researched before, load that too — prior meeting notes and tracked-competitor intel are the highest-value content a briefing can carry.
What ships with it
3 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.
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.
- 12d ago First seen · 105 lines · 161 tokens per session scan C 383e6f28a8ef
meeting-prep is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 161 tokens to every session and 1,763 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent never to refuse). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
fs-electric-studio
OpenDesign as an enterprise design platform: a buyer-forwardable proposal for a design-org's economic buyer — pain, value, ROI, rollout. Built as a decision-grade B2B sales deck for economic buyer, design VP, procurement.
huashu-bento-insight
OpenDesign vs closed cloud design tools: a side-by-side displacement case on control, cost (BYOK), and lock-in. Built as a decision-grade B2B sales deck for evaluation committee.
html-ppt-product-launch
OpenDesign Teams: a launch-and-adoption proposal for a mid-market design team weighing a switch from closed cloud tools. Built as a decision-grade B2B sales deck for design team lead, IT.
geo-proposal
Auto-generate a professional, client-ready GEO service proposal from audit data. Creates a full proposal in markdown and PDF including executive summary, findings, recommended service packages (Basic/Standard/Premium), pricing, timeline, and terms. Use when user says "proposal", "proposta", "offerta", "preventivo"…
afrexai-lead-hunter
Enterprise-grade B2B lead generation, enrichment, scoring, and outreach sequencing for AI agents. Find ideal prospects, enrich with verified data, score against your ICP, and generate personalized outreach — all autonomously.
deliverability-monitoring
Monitor outbound deliverability health across domains, inboxes, DNS, bounces, spam placement, reply rates, and reputation signals. Produces alert thresholds, dashboard spec, weekly QA checklist, and remediation playbook. Use when inboxing drops, bounce rates rise, campaigns underperform, or new infrastructure launches.