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 Doris-Labs/sales-skills --skill meeting-prepgit clone --depth 1 https://github.com/Doris-Labs/sales-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/doris-labs/sales-skills/meeting-prep)<a href="https://agentmods.dev/skills/doris-labs/sales-skills/meeting-prep"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-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/doris-labs/sales-skills/meeting-prep"><img src="https://agentmods.dev/badge/skills/doris-labs/sales-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.00077 | $0.01332 |
| Opus 5 | $0.00039 | $0.00666 |
| Sonnet 5 | $0.00015 | $0.00266 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
meeting-prep 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meeting Prep
Purpose
Turn an upcoming call into a one-page brief the AE can walk in with: who's in the room and what they care about, why this meeting exists, the hypotheses to test, the landmines to avoid, and the single next step you're driving toward.
Inputs
- The meeting (calendar invite, time, title) and who's attending + their roles
- The deal's current stage and what you need this meeting to advance
- Prior history: last calls, open commitments, objections, what's stalled
Method
- Attendee research. For each attendee capture: name, title, role in the deal (champion / economic buyer / blocker / influencer / coach), what they've said before, and what they personally win or lose if this deal moves. New face? Note it and the one question that places them. Identify who's missing that should be there.
- Tight agenda. 3–5 beats, time-boxed, mapped to a goal. Open with a recap + one-line "here's what I want us to leave with." Don't run a feature tour — run the buyer's decision.
- Hypotheses to test. Write 3–5 falsifiable statements you believe about the deal and the exact question that confirms or kills each (e.g. "Budget sits with the VP, not our champion → ask: 'who signs off on spend at this size?'"). The meeting earns its keep by resolving these.
- Landmines / risks to avoid. Known objections, a competitor in the mix, a stalled commitment, a stakeholder who got burned last time, a price-sensitive buyer. For each: the trap and your pre-planned response.
- The single desired next step. One concrete, mutually-owned advance with a date (signed order form, exec intro, security review booked). Everything in the meeting bends toward earning it. If you can't name it, you're not ready.
One-page meeting brief format:
MEETING BRIEF — <account> / <deal> — <date>
Stage: <stage> | Goal of this call: <one line>
WHO (and why they're here)
- <name>, <title> — <role in deal> — cares about: <their win/loss>
- <name>, <title> — <role> — <last thing they said / open item>
- Missing but should attend: <name/role> + how to get them next time
WHY (why this meeting, now)
- <the advance this call exists to create>
WHAT TO ASK (hypotheses → questions)
- <hypothesis> → "<question that confirms/kills it>"
- <hypothesis> → "<question>"
WHAT TO LAND (value to make stick)
- <proof point / value driver tied to their stated pain>
LANDMINES
- <objection / competitor / stalled item> → <your planned response>
THE ASK (single next step)
- <mutually-owned next step> by <date>
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.
- 11d ago First seen · 111 lines · 77 tokens per session scan A eab74468447d
meeting-prep is a skill published in the GitHub repository Doris-Labs/sales-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 77 tokens to every session and 1,332 once invoked, about $0.0004 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.
Other skills, from other repositories
lynqu
Entry point for the Lynqu sales suite — describe any sales situation and it composes the right skills across capture, outreach, quoting and reporting. Requires the Lynqu MCP server connected.
lynqu-sales-playbook
Turn a written sales playbook into a live Lynqu pipeline — contacts, timed tasks, follow-up templates, the playbook attached to each lead, and stage rules that deliver the prep at the right moment.
lynqu-card-studio
Create and update Lynqu digital business cards — contact info, social links, services, template, palette — and check card views, scans and shares. Requires the Lynqu MCP server connected.
lynqu-competitors
Build a battlecard for the incumbent on a Lynqu deal — switching cost, wedge, objections and honest answers — written back to the lead. Requires the Lynqu MCP server.
lynqu-contacts
Map the buying committee on an account — economic buyer, champion, blocker — and write it into Lynqu as contacts and participants. Requires the Lynqu MCP server.
lynqu-deal-desk
Price a Lynqu deal and draft the quote — browse the price book, put priced lines on a deal, then produce a draft quote for a human to send. Requires the Lynqu MCP server connected.