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 agentmods add skills/fergupa/claude_plugins/call-prepnpx skills add fergupa/claude_plugins --skill call-prepgit clone --depth 1 https://github.com/fergupa/claude_pluginsWrote 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/fergupa/claude_plugins/call-prep)<a href="https://agentmods.dev/skills/fergupa/claude_plugins/call-prep"><img src="https://agentmods.dev/badge/skills/fergupa/claude_plugins/call-prep.svg" alt="Measured on agentmods" 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.00082 | $0.01791 |
| Opus 5 | $0.00041 | $0.00896 |
| Sonnet 5 | $0.00016 | $0.00358 |
| Haiku 4.5 | $0.00008 | $0.00179 |
Grade A, and why
call-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 2d 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.
This is a copy
100% identical to call-prep — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Call Prep
Get fully prepared for any sales call in minutes. This skill works with whatever context you provide, and gets significantly better when you connect your sales tools.
How It Works
┌─────────────────────────────────────────────────────────────────┐
│ CALL PREP │
├─────────────────────────────────────────────────────────────────┤
│ ALWAYS (works standalone) │
│ ✓ You tell me: company, meeting type, attendees │
│ ✓ Web search: recent news, funding, leadership changes │
│ ✓ Company research: what they do, size, industry │
│ ✓ Output: prep brief with agenda and questions │
├─────────────────────────────────────────────────────────────────┤
│ SUPERCHARGED (when you connect your tools) │
│ + CRM: account history, contacts, opportunities, activities │
│ + Email: recent threads, open questions, commitments │
│ + Chat: internal discussions, colleague insights │
│ + Transcripts: prior call recordings, key moments │
│ + Calendar: auto-find meeting, pull attendees │
└─────────────────────────────────────────────────────────────────┘
Getting Started
When you run this skill, I'll ask for what I need:
Required:
- Company or contact name
- Meeting type (discovery, demo, negotiation, check-in, etc.)
Helpful if you have it:
- Who's attending (names and titles)
- Any context you want me to know (paste prior notes, emails, etc.)
If you've connected your CRM, email, or other tools, I'll pull context automatically and skip the questions.
Connectors (Optional)
Connect your tools to supercharge this skill:
| Connector | What It Adds |
|---|---|
| CRM | Account details, contact history, open deals, recent activities |
| Recent threads with the company, open questions, attachments shared | |
| Chat | Internal chat discussions (e.g. Slack) about the account, colleague insights |
| Transcripts | Prior call recordings, topics covered, competitor mentions |
| Calendar | Auto-find the meeting, pull attendees and description |
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.
- 2d ago First seen · 259 lines · 82 tokens per session scan A 51b075cf1a1c
call-prep is a skill published in the GitHub repository fergupa/claude_plugins (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 82 tokens to every session and 1,791 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to call-prep, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…