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 charlieviettq/awesome-agent-skill --skill call-prepgit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/call-prep)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/call-prep"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/call-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/charlieviettq/awesome-agent-skill/call-prep"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/call-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.00082 | $0.01756 |
| Opus 5.5 | $0.00033 | $0.00702 |
| Sonnet 5.5 | $0.00016 | $0.00351 |
| Haiku 4.5 | $0.00008 | $0.00176 |
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 1mo 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
95% identical to call-prep — 9 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 — 254 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.
- 1mo ago First seen · 254 lines · 82 tokens per session scan A 626c51415753
call-prep is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 3mo ago), licensed MIT. It adds 82 tokens to every session and 1,756 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to call-prep, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
tool-calling-tutor
Use when a tool-calling agent does not call a tool, sends wrong arguments, loops without stopping, or needs a function schema. Guides a four-branch diagnosis and five-step schema repair. Do not use for framework-specific, MCP-server, or production-observability questions.
dep-auditor
A read-only audit of a project’s third-party packages for known security issues, version health, and license facts. It uses the versions actually selected by lockfiles, which record the exact packages installed, rather than relying only on version ranges.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
env-manager
An environment-variable manager for project settings stored outside the code, often in .env files. It checks variable definitions and usage while keeping secret values out of reports and terminal output.
eslint-fix
A project-aware assistant for finding and fixing ESLint errors, warnings, and configuration compatibility problems. ESLint is a tool that checks JavaScript and TypeScript code for style and common mistakes.